Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 15:42 UTC

pomerium / js-sdk

JavaScript · TypeScriptApache-2.0★ 0 stars⑂ 1 forksince Nov 2022View on GitHub ↗

pomerium/js-sdk holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (79/100) and lowest on Community & Adoption (35/100). It was last updated 1 day 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

PomeriumOrganization
138 followers52 public repossince Dec 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@pomerium/js-sdk1.2.017,119657 days agozero-trustjwtverifypomerium

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
14.5/36Commit cadence — 21/52 weeks with commits
14.8/18Commit volume — 44 commits in the last year
10/10OpenSSF Scorecard: Maintained — 13 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year44
human_commit_share0.627
days_since_last_push1
active_weeks_last_year21
How it's scored
27/27Ships releases — 2 releases published
36/36Release recency — latest release 57 days ago
12.6/27Release cadence — a release every ~274.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv1.2.0
releases_from_tagsno
days_since_latest_release57
mean_days_between_releases274.1
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?

35Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
56.4/80Monthly downloads — 17,119 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@pomerium/js-sdk
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads17,119
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.6/22.5Commit distribution — top contributor authored 53% of commits
8.1/13.5Contributor breadth — 6 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.531
How it's scored
24/42Issue resolution — 57% of issues closed
16.9/30PR acceptance — 66/117 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 14/16 approved changesets -- score normalized to 8
Inputs used
merged_prs66
open_issues3
closed_issues4
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.571
closed_unmerged_prs51
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.4/25Owner reach — 138 followers of pomerium
24.6/25Track record — 52 public repos, account ~7 yr old
Inputs used
followers138
owner_typeOrganization
is_verifiedno
owner_loginpomerium
public_repos52
account_age_days2,821

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 57 days ago
20/20Version history — 6 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@pomerium/js-sdk
ecosystemsnpm
any_deprecatedno
min_days_since_publish57

Engineering Quality

Are baseline engineering and documentation practices in place?

43Weak · 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
4/20OpenSSF Scorecard: CI-Tests — 8 out of 28 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

30At Risk
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.5/2.5CI-Tests — 8 out of 28 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 14/16 approved changesets -- score normalized to 8
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 — 13 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
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:@pomerium/js-sdk@1.2.0 runtime dependency closure — what installing the published package pulls in — 1 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.9/40Legible commit history — 35 of 52 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.673
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
2.4/10Demonstrated agent practice — 1 of the last 83 commits agent-authored or agent-credited
8/8Automated maintenance — 31 of the last 83 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.012
toolchain_manifests—
dependency_bot_commit_share0.373
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/21 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes3,901
source_files_sampled21
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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
6contributors
44commits, last 12 months
1days since last push
2releases
1bus factor
3open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 6.5 / 10
6.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-09-12 15:42 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
2CI-Tests8 out of 28 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 14/16 approved changesets -- score normalized to 8
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmjose^6.1.3package.json
All dependencies 73

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

RegistryPackageVersionRelation
npmjose6.2.10direct
npm@oxfmt/binding-android-arm-eabi0.65.0indirect
npm@oxfmt/binding-android-arm640.65.0indirect
npm@oxfmt/binding-darwin-arm640.65.0indirect
npm@oxfmt/binding-darwin-x640.65.0indirect
npm@oxfmt/binding-freebsd-x640.65.0indirect
npm@oxfmt/binding-linux-arm-gnueabihf0.65.0indirect
npm@oxfmt/binding-linux-arm-musleabihf0.65.0indirect
npm@oxfmt/binding-linux-arm64-gnu0.65.0indirect
npm@oxfmt/binding-linux-arm64-musl0.65.0indirect
npm@oxfmt/binding-linux-ppc64-gnu0.65.0indirect
npm@oxfmt/binding-linux-riscv64-gnu0.65.0indirect
npm@oxfmt/binding-linux-riscv64-musl0.65.0indirect
npm@oxfmt/binding-linux-s390x-gnu0.65.0indirect
npm@oxfmt/binding-linux-x64-gnu0.65.0indirect
npm@oxfmt/binding-linux-x64-musl0.65.0indirect
npm@oxfmt/binding-openharmony-arm640.65.0indirect
npm@oxfmt/binding-win32-arm64-msvc0.65.0indirect
npm@oxfmt/binding-win32-ia32-msvc0.65.0indirect
npm@oxfmt/binding-win32-x64-msvc0.65.0indirect
npm@oxlint/binding-android-arm-eabi1.80.0indirect
npm@oxlint/binding-android-arm641.80.0indirect
npm@oxlint/binding-darwin-arm641.80.0indirect
npm@oxlint/binding-darwin-x641.80.0indirect
npm@oxlint/binding-freebsd-x641.80.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.80.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.80.0indirect
npm@oxlint/binding-linux-arm64-gnu1.80.0indirect
npm@oxlint/binding-linux-arm64-musl1.80.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.80.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.80.0indirect
npm@oxlint/binding-linux-riscv64-musl1.80.0indirect
npm@oxlint/binding-linux-s390x-gnu1.80.0indirect
npm@oxlint/binding-linux-x64-gnu1.80.0indirect
npm@oxlint/binding-linux-x64-musl1.80.0indirect
npm@oxlint/binding-openharmony-arm641.80.0indirect
npm@oxlint/binding-win32-arm64-msvc1.80.0indirect
npm@oxlint/binding-win32-ia32-msvc1.80.0indirect
npm@oxlint/binding-win32-x64-msvc1.80.0indirect
npm@pomerium/js-sdk^1.0.3indirect
npm@pomerium/js-sdk^1.1.0indirect
npm@testing-library/jest-dom^7.0.0indirect
npm@testing-library/react^16.3.1indirect
npm@testing-library/user-event^14.5.2indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmexpress^4.18.2indirect
npmoxfmt0.65.0indirect
npmoxlint1.80.0indirect
npmreact^19.2.3indirect
npmreact-dom^19.2.3indirect
npmreact-scripts5.0.1indirect
npmtinypool2.1.0indirect
npmtypescript7.0.2indirect
npmweb-vitals^6.0.1indirect
Dependency advisories 0

Installing npm:@pomerium/js-sdk@1.2.0 pulls in 1 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 statistics — npm.