Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-31 18:06 UTC

openfort-xyz / shield-js

TypeScript library for seamless integration with the Openfort Shield API. It offers simplified methods for secure authentication and efficient management of secrets, compatible with both Openfort and Custom authentication setups.

TypeScriptNo license detected★ 3 stars⑂ 2 forkssince Mar 2024View on GitHub ↗

openfort-xyz/shield-js holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (73/100) and lowest on Community & Adoption (28/100). It was last updated 9 days ago. 2 contributors account for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

OpenfortOrganization
99 followers70 public repossince Sep 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@openfort/shield-js0.1.3816,556499 days ago

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 recencylast push 9 days ago
11.8/36Commit cadence17/52 weeks with commits
18/18Commit volume137 commits in the last year
9/10OpenSSF Scorecard: Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year137
human_commit_share0.88
days_since_last_push9
active_weeks_last_year17
How it's scored
27/27Ships releases40 releases published
16.2/36Release recencylatest release 233 days ago
27/27Release cadencea release every ~11.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count40
latest_release_tagv0.1.33
releases_from_tagsno
days_since_latest_release233
mean_days_between_releases11.5
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?

28At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars3
watchers0
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
56.3/80Monthly downloads16,556 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@openfort/shield-js
dependents
ecosystemsnpm
total_downloads
monthly_downloads16,556
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?

73Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.7/22.5Commit distributiontop contributor authored 44% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.435
How it's scored
0/42Issue resolutionno issues or no data
28.9/30PR acceptance53/55 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs53
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs2
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
14.4/25Owner reach99 followers of openfort-xyz
20.7/25Track record70 public repos, account ~3 yr old
Inputs used
followers99
owner_typeOrganization
is_verified
owner_loginopenfort-xyz
public_repos70
account_age_days1,400
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 9 days ago
20/20Version history49 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@openfort/shield-js
ecosystemsnpm
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
16/16Linter configbiome.json
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_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/@openfort/shield-js
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsopenfort, shield, nodejs
has_wikiyes
homepagehttps://www.npmjs.com/package/@openfort/shield-js
docs_sitehttps://www.npmjs.com/package/@openfort/shield-js
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
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
0/7.5Code-ReviewFound 0/7 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 4 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
6.8/7.5Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Packaging, 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_packages32
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:@openfort/shield-js@0.1.38 runtime dependency closure — what installing the published package pulls in — 32 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history71 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.807
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/16 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes17,743
source_files_sampled16
oversized_source_files0

Key facts

3GitHub stars
5contributors
137commits, last 12 months
9days since last push
40releases
2bus 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 ★ / 2 ⇿
0Stars
2Forks
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.

111222212024-102025-032025-08
Major 0Minor 0Patch 7
OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-31 18:05 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
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
0Code-ReviewFound 0/7 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
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 2
RegistryPackageVersion constraintManifest
npmaxios1.18.1package.json
npmaxios-retry4.5.0package.json
All dependencies 144

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

RegistryPackageVersionRelation
npmaxios1.18.1direct
npmaxios-retry4.5.0direct
npm@babel/runtime7.28.6indirect
npm@biomejs/biome2.4.4indirect
npm@biomejs/cli-darwin-arm642.4.4indirect
npm@biomejs/cli-darwin-x642.4.4indirect
npm@biomejs/cli-linux-arm642.4.4indirect
npm@biomejs/cli-linux-arm64-musl2.4.4indirect
npm@biomejs/cli-linux-x642.4.4indirect
npm@biomejs/cli-linux-x64-musl2.4.4indirect
npm@biomejs/cli-win32-arm642.4.4indirect
npm@biomejs/cli-win32-x642.4.4indirect
npm@changesets/apply-release-plan7.0.14indirect
npm@changesets/assemble-release-plan6.0.9indirect
npm@changesets/changelog-git0.2.1indirect
npm@changesets/changelog-github0.5.2indirect
npm@changesets/cli2.29.8indirect
npm@changesets/config3.1.2indirect
npm@changesets/errors0.2.0indirect
npm@changesets/get-dependents-graph2.1.3indirect
npm@changesets/get-github-info0.7.0indirect
npm@changesets/get-release-plan4.0.14indirect
npm@changesets/get-version-range-type0.4.0indirect
npm@changesets/git3.0.4indirect
npm@changesets/logger0.1.1indirect
npm@changesets/parse0.4.2indirect
npm@changesets/pre2.0.2indirect
npm@changesets/read0.6.6indirect
npm@changesets/should-skip-package0.1.2indirect
npm@changesets/types4.1.0indirect
npm@changesets/types6.1.0indirect
npm@changesets/write0.4.0indirect
npm@inquirer/external-editor1.0.3indirect
npm@manypkg/find-root1.1.0indirect
npm@manypkg/get-packages1.1.3indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@types/node12.20.55indirect
npmagent-base6.0.2indirect
npmansi-colors4.1.3indirect
npmansi-regex5.0.1indirect
npmargparse2.0.1indirect
npmarray-union2.1.0indirect
npmasynckit0.4.0indirect
npmbetter-path-resolve1.0.0indirect
npmbraces3.0.3indirect
npmcall-bind-apply-helpers1.0.2indirect
npmchardet2.1.1indirect
npmci-info3.9.0indirect
npmcombined-stream1.0.8indirect
npmcross-spawn7.0.6indirect
npmdataloader1.4.0indirect
npmdebug4.4.3indirect
npmdelayed-stream1.0.0indirect
npmdetect-indent6.1.0indirect
npmdir-glob3.0.1indirect
npmdotenv8.6.0indirect
npmdunder-proto1.0.1indirect
npmenquirer2.4.1indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmes-set-tostringtag2.1.0indirect
npmextendable-error0.1.7indirect
npmfast-glob3.3.3indirect
npmfastq1.20.1indirect
npmfill-range7.1.1indirect
npmfind-up4.1.0indirect
npmfollow-redirects1.16.0indirect
npmform-data4.0.6indirect
npmfs-extra7.0.1indirect
npmfs-extra8.1.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmglob-parent5.1.2indirect
npmglobby11.1.0indirect
npmgopd1.2.0indirect
npmgraceful-fs4.2.11indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.4indirect
npmhttps-proxy-agent5.0.1indirect
npmhuman-id4.1.3indirect
npmiconv-lite0.7.2indirect
npmignore5.3.2indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-retry-allowed2.2.0indirect
npmis-subdir1.2.0indirect
npmis-windows1.0.2indirect
npmisexe2.0.0indirect
npmjs-yaml5.2.1indirect
npmjsonfile4.0.0indirect
npmlocate-path5.0.0indirect
npmlodash.startcase4.4.0indirect
npmmath-intrinsics1.1.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmmri1.2.0indirect
npmms2.1.3indirect
npmnode-fetch2.7.0indirect
npmoutdent0.5.0indirect
npmp-filter2.1.0indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-map2.1.0indirect
npmp-try2.2.0indirect
npmpackage-manager-detector0.2.11indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-type4.0.0indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.4indirect
npmpify4.0.1indirect
npmprettier2.8.8indirect
npmproxy-from-env2.1.0indirect
npmquansync0.2.11indirect
npmqueue-microtask1.2.3indirect
npmread-yaml-file1.1.0indirect
npmresolve-from5.0.0indirect
npmreusify1.1.0indirect
npmrun-parallel1.2.0indirect
npmsafer-buffer2.1.2indirect
npmsemver7.7.4indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmslash3.0.0indirect
npmspawndamnit3.0.1indirect
npmstrip-ansi6.0.1indirect
npmstrip-bom3.0.0indirect
npmterm-size2.2.1indirect
npmto-regex-range5.0.1indirect
npmtr460.0.3indirect
npmtypescript5.9.3indirect
npmuniversalify0.1.2indirect
npmwebidl-conversions3.0.1indirect
npmwhatwg-url5.0.0indirect
npmwhich2.0.2indirect
Dependency advisories 0

Installing npm:@openfort/shield-js@0.1.38 pulls in 32 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.27.0 — full methodology · metrics wiki.

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