Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 23:44 UTC

secvisogram / csaf-validator-lib

csaf-validator-lib is a library that can be used to check whether a given CSAF 2.0 document is valid.

JavaScriptMIT★ 4 stars⑂ 9 forkssince Jan 2022View on GitHub ↗

secvisogram/csaf-validator-lib holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (38/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

SecvisogramOrganization
7 followers9 public repossince Mar 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@secvisogram/csaf-validator-lib2.0.283,610662 days agocsafcsaf-validator-libcsaf-full-validatorsecvisogram

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
27.7/36Commit cadence40/52 weeks with commits
18/18Commit volume392 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year392
human_commit_share
days_since_last_push1
active_weeks_last_year40

Release discipline

100Exceptional
How it's scored
27/27Ships releases79 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~14 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count79
latest_release_tagv2.0.28
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases14
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?

38Weak · 17% of overall
How it's scored
7.7/60Stars4 stars
7.5/25Forks9 forks
0/15Watchers0 watchers
Inputs used
forks9
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
47.4/80Monthly downloads3,610 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@secvisogram/csaf-validator-lib
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,610
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.9/22.5Commit distributiontop contributor authored 29% of commits
13.5/13.5Contributor breadth11 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled11
top_contributor_share0.292
How it's scored
23.1/42Issue resolution55% of issues closed
26.3/30PR acceptance338/386 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs338
open_issues107
closed_issues131
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.55
closed_unmerged_prs48
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
6.5/25Owner reach7 followers of secvisogram
18/25Track record9 public repos, account ~5 yr old
Inputs used
followers7
owner_typeOrganization
is_verified
owner_loginsecvisogram
public_repos9
account_age_days1,956
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 2 days ago
20/20Version history66 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@secvisogram/csaf-validator-lib
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicscsaf, csaf-basic-validator, csaf-extended-validator, csaf-full-validator, csaf-validator-lib
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?

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

41Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
46.4/55Manageable file sizes63/405 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes610,975
source_files_sampled405
oversized_source_files63

Key facts

4GitHub stars
11contributors
392commits, last 12 months
1days since last push
79releases
2bus factor
107open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-07-17 23:44 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
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npm@secvisogram/is-leap-second^1.0.0package.json
npmajv^8.11.2package.json
npmajv-formats^3.0.1package.json
npmbcp47^1.1.2package.json
npmcvss2js^1.1.0package.json
npmjson-pointer^0.6.1package.json
npmlodash^4.17.21package.json
npmpackageurl-js^2.0.1package.json
npmsemver^7.5.4package.json
npmtemporal-polyfill^0.3.0package.json
npmundici^6.23.0package.json
All dependencies 132

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

RegistryPackageVersionRelation
npm@secvisogram/is-leap-second1.0.0direct
npmajv8.20.0direct
npmajv-formats3.0.1direct
npmbcp471.1.2direct
npmcvss2js1.1.0direct
npmjson-pointer0.6.2direct
npmlodash4.18.1direct
npmpackageurl-js2.0.1direct
npmsemver7.8.5direct
npmtemporal-polyfill0.3.2direct
npmundici6.27.0direct
npm@bcoe/v8-coverage1.0.2indirect
npm@isaacs/cliui8.0.2indirect
npm@istanbuljs/schema0.1.6indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/chai4.3.20indirect
npm@types/istanbul-lib-coverage2.0.6indirect
npm@types/json-pointer1.0.34indirect
npm@types/lodash4.17.24indirect
npm@types/mocha10.0.10indirect
npm@types/node24.13.3indirect
npm@types/prettier2.7.3indirect
npm@types/semver7.7.1indirect
npm@types/xml2js0.4.14indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmassertion-error1.1.0indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion2.1.2indirect
npmbrace-expansion5.0.7indirect
npmbrowser-stdout1.3.1indirect
npmc810.1.3indirect
npmcamelcase6.3.0indirect
npmchai4.5.0indirect
npmcheck-error1.0.3indirect
npmchokidar5.0.0indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconvert-source-map2.0.0indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdeep-eql4.1.4indirect
npmdiff9.0.0indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.3indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmforeach2.0.6indirect
npmforeground-child3.3.1indirect
npmget-caller-file2.0.5indirect
npmget-func-name2.0.2indirect
npmglob10.5.0indirect
npmglob13.0.6indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmhtml-escaper2.0.2indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmjackspeak3.4.3indirect
npmjs-yaml4.3.0indirect
npmjson-schema-traverse1.0.0indirect
npmlocate-path6.0.0indirect
npmloupe2.3.7indirect
npmlru-cache10.4.3indirect
npmlru-cache11.5.2indirect
npmmake-dir4.0.0indirect
npmminimatch10.2.5indirect
npmminimatch9.0.9indirect
npmminipass7.1.3indirect
npmmocha12.0.0-rc.1indirect
npmms2.1.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpath-scurry2.0.2indirect
npmpathval1.1.1indirect
npmpicocolors1.1.1indirect
npmprettier2.8.8indirect
npmreaddirp5.0.0indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmsax1.6.0indirect
npmserialize-javascript7.0.7indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments5.0.3indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtemporal-spec0.3.1indirect
npmtest-exclude7.0.2indirect
npmtype-detect4.1.0indirect
npmtypescript6.0.3indirect
npmundici-types7.18.2indirect
npmv8-to-istanbul9.3.0indirect
npmwhich2.0.2indirect
npmworkerpool10.0.3indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmxml2js0.5.0indirect
npmxmlbuilder11.0.1indirect
npmy18n5.0.8indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
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.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.