Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-08 06:30 UTC

sam247 / openredaction

Open Source PII detection and redaction for JavaScript/Typescript. Achieve enterprise compliance and unparalleled, lightning fast performance, all 100% local.

TypeScriptMIT★ 98 stars⑂ 19 forkssince Nov 2025View on GitHub ↗
KindWeb interfaceLibraryCommand-line toolhow this is determined

sam247/openredaction holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on Security (51/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

sam247Personal account
1 follower14 public repossince Apr 2013

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@openredaction/cli1.1.5548412 days ago
npm@openredaction/core1.1.55,030412 days ago
npm@openredaction/hono1.0.3344412 days ago
npm@openredaction/react1.1.54,037412 days ago
npmopenredaction1.1.599,1021612 days ago
npm@openredaction/elysia1.0.3349412 days ago
npm@openredaction/server1.1.54,784412 days ago
npm@openredaction/express1.1.54,778412 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
11.1/36Commit cadence — 16/52 weeks with commits
18/18Commit volume — 367 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year367
human_commit_share0.89
days_since_last_push0
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 31 releases published
36/36Release recency — latest release 12 days ago
27/27Release cadence — a release every ~0 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count31
latest_release_tag@openredaction/express@1.1.5
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases0
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?

75Good · 17% of overall
How it's scored
32.2/60Stars — 98 stars
10.5/25Forks — 19 forks
3.3/15Watchers — 5 watchers
Inputs used
forks19
stars98
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
67.7/80Monthly downloads — 118,972 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@openredaction/cli, @openredaction/core, @openredaction/hono, @openredaction/react, openredaction, @openredaction/elysia, @openredaction/server, @openredaction/express
dependents
ecosystemsnpm
total_downloads
monthly_downloads118,972
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?

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.5/22.5Commit distribution — top contributor authored 71% 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.711
How it's scored
38.2/42Issue resolution — 91% of issues closed
15.3/30PR acceptance — 51/100 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/21 approved changesets -- score normalized to 0
Inputs used
merged_prs51
open_issues1
closed_issues10
prs_merged_7d2
prs_decided_7d2
prs_merged_30d14
prs_decided_30d14
issue_closed_ratio0.909
closed_unmerged_prs49
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
2.2/25Owner reach — 1 followers of sam247
20.6/25Track record — 14 public repos, account ~13 yr old
Inputs used
followers1
owner_typeUser
is_verified
owner_loginsam247
public_repos14
account_age_days4,867
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 12 days ago
20/20Version history — 16 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@openredaction/cli, @openredaction/core, @openredaction/hono, @openredaction/react, openredaction, @openredaction/elysia, @openredaction/server, @openredaction/express
ecosystemsnpm
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://openredaction.com
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://openredaction.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2/2.5CI-Tests — 8 out of 10 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/21 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — 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 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
4.5/5SAST — SAST tool detected but not run on all commits
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
0/7.5Vulnerabilities — 74 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
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 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_packages4
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:openredaction@1.1.5 runtime dependency closure — what installing the published package pulls in — 4 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.

73Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 83 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.933
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes2,170
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/cli/tsconfig.json, packages/compat/tsconfig.json, packages/core/tsconfig.json, packages/elysia/tsconfig.json, packages/express/tsconfig.json, packages/hono/tsconfig.json, packages/react/tsconfig.json, packages/server/tsconfig.json, site/docs/tsconfig.json, site/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 24 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 8 of the last 100 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_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configspackages/cli/tsconfig.json, packages/compat/tsconfig.json, packages/core/tsconfig.json, packages/elysia/tsconfig.json, packages/express/tsconfig.json, packages/hono/tsconfig.json, packages/react/tsconfig.json, packages/server/tsconfig.json, site/docs/tsconfig.json, site/tsconfig.json, tsconfig.json
agent_commit_share0.24
toolchain_manifests
dependency_bot_commit_share0.08
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/247 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes46,592
source_files_sampled247
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files

Key facts

98GitHub stars
6contributors
367commits, last 12 months
0days since last push
31releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 19 ⇿
0Stars
19Forks
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.

51015201992025-122026-032026-07
Major 0Minor 0Patch 7
OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-08-08 06:30 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests8 out of 10 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/21 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
9SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities74 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
npm@openredaction/coreworkspace:*site/package.json
npmbotid^1.5.10site/package.json
npmclsx^2.1.0site/package.json
npmlucide-react^0.344.0site/package.json
npmnext16.2.9site/package.json
npmnodemailer^9.0.1site/package.json
npmopenredactionworkspace:*site/package.json
npmreact^19.0.0site/package.json
npmreact-dom^19.0.0site/package.json
npmresend^6.4.2site/package.json
npmtailwind-merge^3.6.0site/package.json
npm@openredaction/coreworkspace:*packages/cli/package.json
npm@openredaction/coreworkspace:*packages/compat/package.json
npm@openredaction/expressworkspace:*packages/compat/package.json
npm@openredaction/reactworkspace:*packages/compat/package.json
npm@openredaction/serverworkspace:*packages/compat/package.json
npm@openredaction/coreworkspace:*packages/elysia/package.json
npm@openredaction/coreworkspace:*packages/express/package.json
npm@openredaction/coreworkspace:*packages/hono/package.json
npm@openredaction/coreworkspace:*packages/react/package.json
npm@openredaction/coreworkspace:*packages/server/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing npm:openredaction@1.1.5 pulls in 4 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

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.5.0, schema v0.31.0 — full methodology · metrics wiki.

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