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

rehydra-ai / rehydra-sdk

Prevent accidental PII leakage in LLM prompts before they hit the model.

TypeScriptMIT★ 82 stars⑂ 9 forkssince Dec 2025View on GitHub ↗

rehydra-ai/rehydra-sdk holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (78/100) and lowest on Security (48/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

rehydra.aiOrganization
1 follower5 public repossince Dec 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmrehydra0.12.03,8143411 days agoanonymizationpiiprivacyneronnx

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
28.8/36Push recency — last push 11 days ago
6.9/36Commit cadence — 10/52 weeks with commits
18/18Commit volume — 167 commits in the last year
10/10OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year167
human_commit_share0.89
days_since_last_push11
active_weeks_last_year10

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 27 releases published
36/36Release recency — latest release 11 days ago
27/27Release cadence — a release every ~13.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count27
latest_release_tagv0.12.0
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases13.3
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?

55Moderate · 17% of overall
How it's scored
31/60Stars — 82 stars
7.5/25Forks — 9 forks
0/15Watchers — 1 watchers
Inputs used
forks9
stars82
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno
How it's scored
47.8/80Monthly downloads — 3,814 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesrehydra
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,814
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.3/22.5Commit distribution — top contributor authored 99% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.987
How it's scored
39.2/42Issue resolution — 93% of issues closed
27.9/30PR acceptance — 54/58 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/19 approved changesets -- score normalized to 0
Inputs used
merged_prs54
open_issues2
closed_issues28
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.933
closed_unmerged_prs4
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of rehydra-ai
6.9/25Track record — 5 public repos, account ~0 yr old
Inputs used
followers1
owner_typeOrganization
is_verified
owner_loginrehydra-ai
public_repos5
account_age_days222

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 11 days ago
20/20Version history — 34 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesrehydra
ecosystemsnpm
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.cjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 13 out of 25 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://playground.rehydra.ai
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsai-security, gdpr, llm-security, pii, privacy
has_wikiyes
homepagehttps://playground.rehydra.ai
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

48Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.2/2.5CI-Tests — 13 out of 25 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/19 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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
0/7.5Vulnerabilities — 39 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): signed_releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
10/25Indirect dependencies free of known advisories — 1 affected: adm-zip 0.5.18 (high 7.5)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages17
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:rehydra@0.12.0 runtime dependency closure — what installing the published package pulls in — 17 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)
39.6/40Legible commit history — 66 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.742
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.cjs
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/185 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes49,714
source_files_sampled185
oversized_source_files0

Key facts

82GitHub stars
3contributors
167commits, last 12 months
11days since last push
27releases
1bus factor
2open 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 ★ / 9 ⇿
0Stars
9Forks
21Releases

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.

0246810912026-022026-052026-07
Major 0Minor 7Patch 14
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-06 00:04 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests13 out of 25 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/19 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
0Vulnerabilities39 existing vulnerabilities detected
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 1

Installing npm:rehydra@0.12.0 pulls in 17 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
adm-zip0.5.18indirecthigh10.6.0

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.