Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 07:54 UTC

NodeSecure / scanner

⚡️ A package API to run a static analysis of your module's dependencies. This is the CLI engine!

TypeScriptMIT★ 40 stars⑂ 23 forkssince Jun 2021View on GitHub ↗

NodeSecure/scanner holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on Community & Adoption (57/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

89
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.

89
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 75 is calibrated to 89 on the published index scale (record calibration 2026-08-02).

Ownership

NodeSecureOrganization
162 followers35 public repossince Jun 2021

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@nodesecure/rc5.6.05,31423173 days agorcconfigconfiguration
npm@nodesecure/i18n4.1.14,0252838 days agoi18nnodesecure
npm@nodesecure/mama2.4.02,2121669 days agomanifestmanagerpacotesecurity
npm@nodesecure/flagspoints to another repo — not scored3.0.33,60013474 days agonodesecureflagsdocumentation
npm@nodesecure/utils2.3.02,6808457 days agoutilsnsecurenodesecure
npm@nodesecure/github2.1.0576329 days agonodesecuregithubdownloadarchive
npm@nodesecure/gitlab2.1.0244329 days agonodesecuregitlab
npm@nodesecure/contact3.3.01,637869 days agoauthorcontactmaintainer

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
27/36Commit cadence — 39/52 weeks with commits
18/18Commit volume — 185 commits in the last year
10/10OpenSSF Scorecard: Maintained — 21 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year185
human_commit_share0.61
days_since_last_push10
active_weeks_last_year39

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 38 days ago
27/27Release cadence — a release every ~13.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag@nodesecure/tree-walker@4.0.3
releases_from_tagsno
days_since_latest_release38
mean_days_between_releases13.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

57Moderate · 17% of overall
How it's scored
25.8/60Stars — 40 stars
11.2/25Forks — 23 forks
0/15Watchers — 2 watchers
Inputs used
forks23
stars40
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapi.securityscorecards.dev, shields.io
has_pull_request_templateno
How it's scored
56/80Monthly downloads — 15,949 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@nodesecure/rc, @nodesecure/i18n, @nodesecure/mama, @nodesecure/utils, @nodesecure/github, @nodesecure/gitlab, @nodesecure/contact
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads15,949
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?

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.7/22.5Commit distribution — top contributor authored 75% of commits
13.5/13.5Contributor breadth — 23 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.747
How it's scored
38/42Issue resolution — 90% of issues closed
21.7/30PR acceptance — 464/642 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs464
open_issues11
closed_issues104
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.904
closed_unmerged_prs178
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
15.9/25Owner reach — 162 followers of NodeSecure
21.9/25Track record — 35 public repos, account ~5 yr old
Inputs used
followers162
owner_typeOrganization
is_verifiedno
owner_loginNodeSecure
public_repos35
account_age_days1,932

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on npm
35/35Publish recency — latest publish 38 days ago
20/20Version history — 28 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@nodesecure/rc, @nodesecure/i18n, @nodesecure/mama, @nodesecure/utils, @nodesecure/github, @nodesecure/gitlab, @nodesecure/contact
ecosystemsnpm
any_deprecatedno
min_days_since_publish38

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 26 out of 28 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsnodesecure, nodejs, security, scanner, audit, sast
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

80Excellent · 16% of overall

Security posture

80Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 26 out of 28 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 17 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 21 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
3.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
10/25Indirect dependencies free of known advisories — 1 affected: undici 7.24.4 (high 7.5)
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 91 days ago
Inputs used
sourceosv
advisories12
affected_packages1
assessed_packages299
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:@nodesecure/rc@5.6.0 runtime dependency closure — what installing the published package pulls in — 299 packages. 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.

65Good · 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 — 61 of 61 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
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — tsconfig.json, workspaces/conformance/tsconfig.json, workspaces/contact/test/tsconfig.json, workspaces/contact/tsconfig.json, workspaces/flags/tsconfig.json, workspaces/fs-walk/tsconfig.json, workspaces/github/tsconfig.json, workspaces/gitlab/tsconfig.json, workspaces/i18n/tsconfig.json, workspaces/mama/test/tsconfig.json, workspaces/mama/tsconfig.json, workspaces/npm-types/tsconfig.json, workspaces/opencode-nodesecure/tsconfig.json, workspaces/rc/tsconfig.json, workspaces/scanner/test/tsconfig.json, workspaces/scanner/tsconfig.json, workspaces/tarball/test/tsconfig.json, workspaces/tarball/tsconfig.json, workspaces/tree-walker/tsconfig.json, workspaces/utils/tsconfig.json
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 21 of the last 100 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json, workspaces/conformance/tsconfig.json, workspaces/contact/test/tsconfig.json, workspaces/contact/tsconfig.json, workspaces/flags/tsconfig.json, workspaces/fs-walk/tsconfig.json, workspaces/github/tsconfig.json, workspaces/gitlab/tsconfig.json, workspaces/i18n/tsconfig.json, workspaces/mama/test/tsconfig.json, workspaces/mama/tsconfig.json, workspaces/npm-types/tsconfig.json, workspaces/opencode-nodesecure/tsconfig.json, workspaces/rc/tsconfig.json, workspaces/scanner/test/tsconfig.json, workspaces/scanner/tsconfig.json, workspaces/tarball/test/tsconfig.json, workspaces/tarball/tsconfig.json, workspaces/tree-walker/tsconfig.json, workspaces/utils/tsconfig.json
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.21
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.8/55Manageable file sizes — 1/242 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes96,825
source_files_sampled242
oversized_source_files1

Key facts

40GitHub stars
23contributors
185commits, last 12 months
10days since last push
100releases
1bus factor
11open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package '@nodesecure/flags' points at a different repository (https://github.com/NodeSecure/flags); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 23 ⇿
0Stars
23Forks
91Releases

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.

048121620242322021-082023-122026-04
Major 0Minor 0Patch 0

Each point covers 5 days.

OpenSSF Scorecard 8.0 / 10
8.0aggregate

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-18 07:53 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9CI-Tests26 out of 28 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained21 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 69
RegistryPackageVersion constraintManifest
npm@nodesecure/mama^2.1.0workspaces/conformance/package.json
npm@openally/result3.1.0workspaces/conformance/package.json
npmastring^1.9.0workspaces/conformance/package.json
npmfastest-levenshtein^1.0.16workspaces/conformance/package.json
npmspdx-expression-parse^5.0.0workspaces/conformance/package.json
npm@nodesecure/npm-types^1.2.0workspaces/contact/package.json
npmtype-fest^5.0.1workspaces/contact/package.json
npm@openally/httpie1.1.4workspaces/github/package.json
npmtar-fs^3.0.5workspaces/github/package.json
npm@openally/httpie1.1.4workspaces/gitlab/package.json
npmtar-fs^3.0.6workspaces/gitlab/package.json
npm@nodesecure/js-x-ray16.0.0workspaces/i18n/package.json
npmcacache^21.0.0workspaces/i18n/package.json
npmdeepmerge^4.3.1workspaces/i18n/package.json
npmlodash.get^4.4.2workspaces/i18n/package.json
npm@nodesecure/npm-types^1.4.0workspaces/mama/package.json
npm@nodesecure/utils^2.3.0workspaces/mama/package.json
npm@nodesecure/contact^3.3.0workspaces/mama/package.json
npmobject-hash^3.0.0workspaces/mama/package.json
npmssri14.0.0workspaces/mama/package.json
npm@nodesecure/scanner^10.4.0workspaces/opencode-nodesecure/package.json
npm@opencode-ai/plugin^1.2.10workspaces/opencode-nodesecure/package.json
npm@nodesecure/js-x-ray16.0.0workspaces/rc/package.json
npm@nodesecure/npm-types^1.2.0workspaces/rc/package.json
npm@nodesecure/vulnera3.1.0workspaces/rc/package.json
npm@openally/config^2.0.0workspaces/rc/package.json
npm@openally/result3.1.0workspaces/rc/package.json
npmlodash.merge^4.6.2workspaces/rc/package.json
npmtype-fest^5.0.1workspaces/rc/package.json
npm@fastify/deepmerge^3.1.0workspaces/scanner/package.json
npm@nodesecure/conformance^1.2.1workspaces/scanner/package.json
npm@nodesecure/contact^3.3.0workspaces/scanner/package.json
npm@nodesecure/flags^3.0.3workspaces/scanner/package.json
npm@nodesecure/i18n^4.1.0workspaces/scanner/package.json
npm@nodesecure/js-x-ray16.0.0workspaces/scanner/package.json
npm@nodesecure/mama^2.4.0workspaces/scanner/package.json
npm@nodesecure/npm-registry-sdk4.5.2workspaces/scanner/package.json
npm@nodesecure/npm-types^1.4.0workspaces/scanner/package.json
npm@nodesecure/rc^5.6.0workspaces/scanner/package.json
npm@nodesecure/tarball^4.2.0workspaces/scanner/package.json
npm@nodesecure/tree-walker^4.0.2workspaces/scanner/package.json
npm@nodesecure/utils^2.3.0workspaces/scanner/package.json
npm@nodesecure/vulnera3.1.0workspaces/scanner/package.json
npm@openally/mutex^3.0.0workspaces/scanner/package.json
npmfastest-levenshtein^1.0.16workspaces/scanner/package.json
npmfrequency-set^2.1.0workspaces/scanner/package.json
npmpacote^22.0.0workspaces/scanner/package.json
npmsemver^7.5.4workspaces/scanner/package.json
npmtype-fest^5.0.1workspaces/scanner/package.json
npm@nodesecure/conformance^1.2.1workspaces/tarball/package.json
npm@nodesecure/fs-walk^2.0.0workspaces/tarball/package.json
npm@nodesecure/js-x-ray16.0.0workspaces/tarball/package.json
npm@nodesecure/mama^2.3.1workspaces/tarball/package.json
npm@nodesecure/npm-types^1.2.0workspaces/tarball/package.json
npm@nodesecure/utils^2.3.0workspaces/tarball/package.json
npm@openally/result3.1.0workspaces/tarball/package.json
npmhyperid4.0.0workspaces/tarball/package.json
npmipaddr.js2.5.0workspaces/tarball/package.json
npmpacote^22.0.0workspaces/tarball/package.json
npm@nodesecure/js-x-ray16.0.0workspaces/tree-walker/package.json
npm@nodesecure/mama2.4.0workspaces/tree-walker/package.json
npm@nodesecure/npm-registry-sdk4.5.2workspaces/tree-walker/package.json
npm@nodesecure/npm-types^1.4.0workspaces/tree-walker/package.json
npm@npmcli/arborist10.0.2workspaces/tree-walker/package.json
npmcombine-async-iterators^3.0.0workspaces/tree-walker/package.json
npmitertools^2.3.1workspaces/tree-walker/package.json
npmnpm-pick-manifest^12.0.0workspaces/tree-walker/package.json
npmpacote^22.0.0workspaces/tree-walker/package.json
npmsemver^7.6.0workspaces/tree-walker/package.json
All dependencies 77

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

RegistryPackageVersionRelation
npm@fastify/deepmerge^3.1.0direct
npm@nodesecure/conformance^1.2.1direct
npm@nodesecure/contact^3.3.0direct
npm@nodesecure/flags^3.0.3direct
npm@nodesecure/fs-walk^2.0.0direct
npm@nodesecure/i18n^4.1.0direct
npm@nodesecure/js-x-ray16.0.0direct
npm@nodesecure/mama2.4.0direct
npm@nodesecure/mama^2.1.0direct
npm@nodesecure/mama^2.3.1direct
npm@nodesecure/mama^2.4.0direct
npm@nodesecure/npm-registry-sdk4.5.2direct
npm@nodesecure/npm-types^1.2.0direct
npm@nodesecure/npm-types^1.4.0direct
npm@nodesecure/rc^5.6.0direct
npm@nodesecure/scanner^10.4.0direct
npm@nodesecure/tarball^4.2.0direct
npm@nodesecure/tree-walker^4.0.2direct
npm@nodesecure/utils^2.3.0direct
npm@nodesecure/vulnera3.1.0direct
npm@npmcli/arborist10.0.2direct
npm@openally/config^2.0.0direct
npm@openally/httpie1.1.4direct
npm@openally/mutex^3.0.0direct
npm@openally/result3.1.0direct
npm@opencode-ai/plugin^1.2.10direct
npmastring^1.9.0direct
npmcacache^21.0.0direct
npmcombine-async-iterators^3.0.0direct
npmdeepmerge^4.3.1direct
npmfastest-levenshtein^1.0.16direct
npmfrequency-set^2.1.0direct
npmhyperid4.0.0direct
npmipaddr.js2.5.0direct
npmitertools^2.3.1direct
npmlodash.get^4.4.2direct
npmlodash.merge^4.6.2direct
npmnpm-pick-manifest^12.0.0direct
npmobject-hash^3.0.0direct
npmpacote^22.0.0direct
npmsemver^7.5.4direct
npmsemver^7.6.0direct
npmspdx-expression-parse^5.0.0direct
npmssri14.0.0direct
npmtar-fs^3.0.5direct
npmtar-fs^3.0.6direct
npmtype-fest^5.0.1direct
npm@arethetypeswrong/cli^0.18.2indirect
npm@changesets/changelog-github^0.7.0indirect
npm@changesets/cli^2.29.4indirect
npm@faker-js/faker^10.0.0indirect
npm@npmcli/config^10.4.2indirect
npm@openally/config.eslint^2.4.2indirect
npm@openally/config.typescript1.3.0indirect
npm@slimio/is^2.0.0indirect
npm@types/lodash.get^4.4.9indirect
npm@types/lodash.merge^4.6.7indirect
npm@types/node^26.0.0indirect
npm@types/npmcli__arborist^6.3.0indirect
npm@types/npmcli__config^6.0.3indirect
npm@types/object-hash^3.0.6indirect
npm@types/pacote^11.1.8indirect
npm@types/semver^7.5.8indirect
npm@types/spdx-expression-parse^4.0.0indirect
npm@types/tar-fs^2.0.4indirect
npm@types/turndown^5.0.5indirect
npm@types/zen-observable^0.8.4indirect
npmajv8.20.0indirect
npmc8^11.0.0indirect
npmesbuild0.28.1indirect
npmget-folder-size^5.0.0indirect
npmnode-estree^4.0.0indirect
npmpkg-ok^4.0.0indirect
npmtsd^0.33.0indirect
npmturndown^7.1.2indirect
npmtypescript6.0.3indirect
npmzup^0.0.2indirect
Dependency advisories 1

Installing npm:@nodesecure/rc@5.6.0 pulls in 299 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
undici7.24.4indirecthigh128.9.0

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.