Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-25 23:55 UTC

panva / dpop

DPoP for Web Platform API JavaScript runtimes

TypeScript · JavaScriptMIT★ 61 stars⑂ 10 forkssince Mar 2020View on GitHub ↗

panva/dpop holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Security (82/100) and lowest on Engineering Quality (59/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

80
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 68 is calibrated to 80 on the published index scale (record calibration 2026-08-02).

Ownership

Filip SkokanPersonal account
1,714 followers75 public repossince Apr 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmdpop2.1.25,487,0921932 days agodpoprfc9449

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

72Good · 21% of overall
How it's scored
28.8/36Push recency — last push 11 days ago
11.8/36Commit cadence — 17/52 weeks with commits
13.1/18Commit volume — 28 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year28
human_commit_share0.724
days_since_last_push11
active_weeks_last_year17
How it's scored
27/27Ships releases — 8 releases published
36/36Release recency — latest release 32 days ago
12.6/27Release cadence — a release every ~173.7 days
8/10OpenSSF Scorecard: Signed-Releases — 1 out of the last 1 releases have a total of 1 signed artifacts.
Inputs used
releases_count8
latest_release_tagv2.1.2
releases_from_tagsno
days_since_latest_release32
mean_days_between_releases173.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

70Good · 17% of overall
How it's scored
28.8/60Stars — 61 stars
8/25Forks — 10 forks
1.7/15Watchers — 3 watchers
Inputs used
forks10
stars61
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 5,487,092 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdpop
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,487,092
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.4/22.5Commit distribution — top contributor authored 98% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.982
How it's scored
0/42Issue resolution — no issues or no data
26.7/30PR acceptance — 16/18 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs16
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
23.3/25Owner reach — 1,714 followers of panva
25/25Track record — 75 public repos, account ~16 yr old
Inputs used
followers1,714
owner_typeUser
is_verified—
owner_loginpanva
public_repos75
account_age_days6,011
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 32 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdpop
ecosystemsnpm
any_deprecatedno
min_days_since_publish32

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 1 out of 11 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsoauth2, dpop, oauth
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 1 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/19 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 6 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
6/7.5Signed-Releases — 1 out of the last 1 releases have a total of 1 signed artifacts.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.8
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages116
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 116 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 55 of 55 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 76
8/8Automated maintenance — 14 of the last 76 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.184
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/3 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes11,516
source_files_sampled3
oversized_source_files0

Key facts

61GitHub stars
2contributors
28commits, last 12 months
11days since last push
8releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 10 ⇿
0Stars
10Forks
7Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

2468101022022-082024-072026-07
Major 1Minor 4Patch 2

Each point covers 4 days.

OpenSSF Scorecard 7.8 / 10
7.8aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-25 23:55 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests1 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/19 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases1 out of the last 1 releases have a total of 1 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
6Vulnerabilities4 existing vulnerabilities detected
All dependencies 116

Full resolved dependency set from the GitHub dependency graph: 0 direct and 116 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@gerrit0/mini-shiki1.27.2indirect
npm@shikijs/engine-oniguruma1.29.2indirect
npm@shikijs/types1.29.2indirect
npm@shikijs/vscode-textmate10.0.2indirect
npm@types/debug4.1.12indirect
npm@types/hast3.0.4indirect
npm@types/mdast4.0.4indirect
npm@types/ms2.1.0indirect
npm@types/unist3.0.3indirect
npm@yarnpkg/lockfile1.1.0indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbinary-searching2.0.5indirect
npmbrace-expansion2.1.0indirect
npmbraces3.0.3indirect
npmcall-bind1.0.8indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmchalk4.1.2indirect
npmcharacter-entities2.0.2indirect
npmci-info3.9.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcomment-parser1.4.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.1indirect
npmdecode-named-character-reference1.2.0indirect
npmdefine-data-property1.1.4indirect
npmdequal2.0.3indirect
npmdevlop1.1.0indirect
npmdunder-proto1.0.1indirect
npmentities4.5.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmfast-check4.9.0indirect
npmfill-range7.1.1indirect
npmfind-yarn-workspace-root2.0.0indirect
npmfs-extra10.1.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhas-property-descriptors1.0.2indirect
npmhas-symbols1.1.0indirect
npmhasown2.0.2indirect
npmis-docker2.2.1indirect
npmis-number7.0.0indirect
npmis-wsl2.2.0indirect
npmisarray2.0.5indirect
npmisexe2.0.0indirect
npmjson-stable-stringify1.3.0indirect
npmjsonfile6.2.0indirect
npmjsonify0.0.1indirect
npmklaw-sync6.0.0indirect
npmlinkify-it5.0.2indirect
npmlunr2.3.9indirect
npmmarkdown-it14.2.0indirect
npmmath-intrinsics1.1.0indirect
npmmdast-util-from-markdown2.0.2indirect
npmmdast-util-to-string4.0.0indirect
npmmdurl2.0.0indirect
npmmicromark4.0.2indirect
npmmicromark-core-commonmark2.0.3indirect
npmmicromark-factory-destination2.0.1indirect
npmmicromark-factory-label2.0.1indirect
npmmicromark-factory-space2.0.1indirect
npmmicromark-factory-title2.0.1indirect
npmmicromark-factory-whitespace2.0.1indirect
npmmicromark-util-character2.1.1indirect
npmmicromark-util-chunked2.0.1indirect
npmmicromark-util-classify-character2.0.1indirect
npmmicromark-util-combine-extensions2.0.1indirect
npmmicromark-util-decode-numeric-character-reference2.0.2indirect
npmmicromark-util-decode-string2.0.1indirect
npmmicromark-util-encode2.0.1indirect
npmmicromark-util-html-tag-name2.0.1indirect
npmmicromark-util-normalize-identifier2.0.1indirect
npmmicromark-util-resolve-all2.0.1indirect
npmmicromark-util-sanitize-uri2.0.1indirect
npmmicromark-util-subtokenize2.1.0indirect
npmmicromark-util-symbol2.0.1indirect
npmmicromark-util-types2.0.2indirect
npmmicromatch4.0.8indirect
npmminimatch9.0.9indirect
npmminimist1.2.8indirect
npmms2.1.3indirect
npmobject-keys1.1.1indirect
npmopen7.4.2indirect
npmpatch-package8.0.1indirect
npmpath-key3.1.1indirect
npmpicomatch2.3.2indirect
npmprettier3.5.3indirect
npmprettier-plugin-jsdoc1.3.2indirect
npmpunycode.js2.3.1indirect
npmpure-rand8.4.2indirect
npmsemver7.7.2indirect
npmset-function-length1.2.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmslash2.0.0indirect
npmsupports-color7.2.0indirect
npmtmp0.2.7indirect
npmto-regex-range5.0.1indirect
npmtypedoc0.27.9indirect
npmtypedoc-plugin-markdown4.3.1indirect
npmtypedoc-plugin-mdn-links4.0.3indirect
npmtypescript5.8.3indirect
npmuc.micro2.1.0indirect
npmunist-util-stringify-position4.0.0indirect
npmuniversalify2.0.1indirect
npmwhich2.0.2indirect
npmyaml2.8.0indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 116 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion2.1.0indirecthigh35.0.9
yaml2.8.0indirectmoderate12.8.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.