Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 01:55 UTC

postalsys / certs

Manage certificates

JavaScriptNo license detected★ 0 stars⑂ 0 forkssince Jun 2022View on GitHub ↗

postalsys/certs holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (81/100) and lowest on Community & Adoption (23/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

Postal SystemsOrganization · verified domain
42 followers31 public repossince May 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@postalsys/certs1.4.22,014282 days ago

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
7.6/36Commit cadence11/52 weeks with commits
15.2/18Commit volume48 commits in the last year
10/10OpenSSF Scorecard: Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year48
human_commit_share0.699
days_since_last_push2
active_weeks_last_year11

Release discipline

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

23At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
44.1/80Monthly downloads2,014 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@postalsys/certs
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,014
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance22/22 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/18 approved changesets -- score normalized to 0
Inputs used
merged_prs22
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs0
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
30/30Ownership backingorganization-owned
20/20Verified domain
11.7/25Owner reach42 followers of postalsys
23/25Track record31 public repos, account ~6 yr old
Inputs used
followers42
owner_typeOrganization
is_verifiedyes
owner_loginpostalsys
public_repos31
account_age_days2,308

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
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?

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests1 out of 12 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/18 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages34
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@postalsys/certs@1.4.2 runtime dependency closure — what installing the published package pulls in — 34 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.

72Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history44 of 51 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.863
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes10,417
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc
0/11Static type checking
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice11 of the last 73 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.151
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/25 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes51,353
source_files_sampled25
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
1contributors
48commits, last 12 months
2days since last push
22releases
1bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-14 01:54 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests1 out of 12 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/18 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@msgpack/msgpack3.1.3package.json
npmioredfour1.4.3package.json
npmjoi18.2.9package.json
npmpino10.3.1package.json
npmpunycode.js2.3.1package.json
npmundici7.29.1package.json
All dependencies 179

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

RegistryPackageVersionRelation
npm@msgpack/msgpack3.1.3direct
npmioredfour1.4.3direct
npmjoi18.2.9direct
npmpino10.3.1direct
npmpunycode.js2.3.1direct
npmundici7.29.1direct
npm@cacheable/memory2.2.0indirect
npm@cacheable/utils2.5.0indirect
npm@eslint-community/eslint-utils4.10.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.5indirect
npm@eslint/config-helpers0.7.0indirect
npm@eslint/core1.2.1indirect
npm@eslint/object-schema3.0.5indirect
npm@eslint/plugin-kit0.7.3indirect
npm@hapi/address5.1.1indirect
npm@hapi/formula3.0.2indirect
npm@hapi/hoek11.0.7indirect
npm@hapi/pinpoint2.0.1indirect
npm@hapi/tlds1.1.7indirect
npm@hapi/topo6.0.2indirect
npm@humanfs/core0.19.2indirect
npm@humanfs/node0.16.8indirect
npm@humanfs/types0.15.0indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@ioredis/commands2.0.0indirect
npm@keyv/bigmap1.3.1indirect
npm@keyv/serialize1.1.1indirect
npm@pinojs/redact0.4.0indirect
npm@standard-schema/spec1.1.0indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.9indirect
npm@types/json-schema7.0.15indirect
npmaccepts1.3.8indirect
npmacorn8.18.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.15.0indirect
npmarray-flatten1.1.1indirect
npmatomic-sleep1.0.0indirect
npmbalanced-match4.0.4indirect
npmbody-parser1.20.8indirect
npmbrace-expansion5.0.9indirect
npmbytes3.1.2indirect
npmcacheable2.5.0indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcluster-key-slot1.1.1indirect
npmcontent-disposition0.5.4indirect
npmcontent-type1.0.5indirect
npmcookie0.7.2indirect
npmcookie-signature1.0.7indirect
npmcross-spawn7.0.6indirect
npmdebug2.6.9indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmdenque2.1.0indirect
npmdepd2.0.0indirect
npmdestroy1.2.0indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.2indirect
npmescape-html1.0.3indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.10.0indirect
npmeslint-config-nodemailer1.2.0indirect
npmeslint-config-prettier9.1.0indirect
npmeslint-scope9.1.2indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys5.0.1indirect
npmespree11.2.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmetag1.8.1indirect
npmexpress4.22.2indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache11.1.5indirect
npmfinalhandler1.3.2indirect
npmfind-up5.0.0indirect
npmflat-cache6.1.23indirect
npmflatted3.4.4indirect
npmforwarded0.2.0indirect
npmfresh0.5.2indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmglob-parent6.0.2indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhashery1.5.1indirect
npmhasown2.0.4indirect
npmhookified1.15.1indirect
npmhookified2.2.0indirect
npmhttp-errors2.0.1indirect
npmiconv-lite0.4.24indirect
npmignore5.3.2indirect
npmimurmurhash0.1.4indirect
npminherits2.0.4indirect
npmioredis6.0.0indirect
npmipaddr.js1.9.1indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv5.6.0indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer0.3.0indirect
npmmerge-descriptors1.0.3indirect
npmmethods1.1.2indirect
npmmime1.6.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmminimatch10.2.6indirect
npmms2.0.0indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmnegotiator0.6.3indirect
npmobject-inspect1.13.4indirect
npmon-exit-leak-free2.1.2indirect
npmon-finished2.4.1indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparseurl1.3.3indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-to-regexp0.1.13indirect
npmpino-abstract-transport3.0.0indirect
npmpino-std-serializers7.1.0indirect
npmprelude-ls1.2.1indirect
npmprocess-warning5.1.0indirect
npmproxy-addr2.0.7indirect
npmpunycode2.3.1indirect
npmqified0.10.1indirect
npmqs6.15.3indirect
npmqs6.16.0indirect
npmquick-format-unescaped4.0.4indirect
npmrange-parser1.2.1indirect
npmraw-body2.5.3indirect
npmreal-require0.2.0indirect
npmreal-require1.0.0indirect
npmredis-errors1.2.0indirect
npmsafe-buffer5.2.1indirect
npmsafe-stable-stringify2.5.0indirect
npmsafer-buffer2.1.2indirect
npmsend0.19.2indirect
npmserve-static1.16.3indirect
npmsetprototypeof1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.1indirect
npmside-channel-list1.0.1indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmsonic-boom4.2.1indirect
npmsplit24.2.0indirect
npmstandard-as-callback2.1.0indirect
npmstatuses2.0.2indirect
npmthread-stream4.2.0indirect
npmtoidentifier1.0.1indirect
npmtype-check0.4.0indirect
npmtype-is1.6.18indirect
npmunpipe1.0.0indirect
npmuri-js4.4.1indirect
npmutils-merge1.0.1indirect
npmvary1.1.2indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:@postalsys/certs@1.4.2 pulls in 34 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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