Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 22:27 UTC

somus / pipr

Code-owned AI review for pull requests

TypeScriptMIT★ 4 stars⑂ 0 forkssince Jul 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

somus/pipr holds a health index of 75 out of 100, placing it in the Good band. It scores highest on AI Readiness (92/100) and lowest on Community & Adoption (43/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Somasundaram AyyappanPersonal account
77 followers34 public repossince Jun 2012

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@usepipr/cli0.9.14362811 days ago
npm@usepipr/sdk0.9.15162811 days ago
npm@usepipr/runtime0.9.15122811 days ago

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
5.5/36Commit cadence — 8/52 weeks with commits
18/18Commit volume — 167 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year167
human_commit_share1
days_since_last_push2
active_weeks_last_year8
How it's scored
27/27Ships releases — 28 releases published
36/36Release recency — latest release 11 days ago
27/27Release cadence — a release every ~9.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count28
latest_release_tagv0.9.1
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases9.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

43Weak · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars4
watchers0
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
42.2/80Monthly downloads — 1,464 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@usepipr/cli, @usepipr/sdk, @usepipr/runtime
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,464
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?

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
28.9/30PR acceptance — 154/160 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs154
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d8
prs_decided_30d8
issue_closed_ratio—
closed_unmerged_prs6
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
13.6/25Owner reach — 77 followers of somus
23.2/25Track record — 34 public repos, account ~14 yr old
Inputs used
followers77
owner_typeUser
is_verified—
owner_loginsomus
public_repos34
account_age_days5,255
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on npm
35/35Publish recency — latest publish 11 days ago
20/20Version history — 28 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@usepipr/cli, @usepipr/sdk, @usepipr/runtime
ecosystemsnpm
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsai-code-review, bun, code-review, developer-tools, github-actions, pull-requests, review-automation, typescript
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 38 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection. 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_packages173
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:@usepipr/cli@0.9.1 runtime dependency closure — what installing the published package pulls in — 173 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.

92Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://pipr.run/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://pipr.run/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes8,840
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — .pipr/tsconfig.json, apps/docs/tsconfig.json, packages/cli/tsconfig.json, packages/e2e/tsconfig.json, packages/evals/tsconfig.json, packages/runtime/tsconfig.json, packages/sdk/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configyes
typecheck_configs.pipr/tsconfig.json, apps/docs/tsconfig.json, packages/cli/tsconfig.json, packages/e2e/tsconfig.json, packages/evals/tsconfig.json, packages/runtime/tsconfig.json, packages/sdk/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.6/55Manageable file sizes — 4/502 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes89,542
source_files_sampled502
oversized_source_files4
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 — recipes
Inputs used
example_dirsrecipes
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

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-10-21 22:27 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
10CI-Tests25 out of 25 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/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities38 existing vulnerabilities detected
Direct dependencies 34
RegistryPackageVersion constraintManifest
npm@usepipr/sdk0.9.1.pipr/package.json
npm@actions/core3.0.1packages/cli/package.json
npm@usepipr/runtime0.9.1packages/cli/package.json
npm@usepipr/sdk0.9.1packages/cli/package.json
npmcommander15.0.0packages/cli/package.json
npm@earendil-works/pi-ai1.0.4packages/e2e/package.json
npm@usepipr/runtimeworkspace:*packages/e2e/package.json
npm@earendil-works/pi-ai1.0.4packages/evals/package.json
npm@usepipr/runtimeworkspace:*packages/evals/package.json
npm@usepipr/sdkworkspace:*packages/evals/package.json
npmzod4.4.3packages/evals/package.json
npm@earendil-works/chord1.0.4packages/runtime/package.json
npm@earendil-works/pi-ai1.0.4packages/runtime/package.json
npm@earendil-works/pi-durable1.0.4packages/runtime/package.json
npm@octokit/rest22.0.1packages/runtime/package.json
npm@opentelemetry/api1.9.1packages/runtime/package.json
npm@opentelemetry/exporter-logs-otlp-proto0.220.0packages/runtime/package.json
npm@opentelemetry/exporter-metrics-otlp-proto0.220.0packages/runtime/package.json
npm@opentelemetry/exporter-trace-otlp-proto0.220.0packages/runtime/package.json
npm@opentelemetry/resources2.9.0packages/runtime/package.json
npm@opentelemetry/sdk-logs0.220.0packages/runtime/package.json
npm@opentelemetry/sdk-metrics2.9.0packages/runtime/package.json
npm@opentelemetry/sdk-trace-base2.9.0packages/runtime/package.json
npm@opentelemetry/semantic-conventions1.43.0packages/runtime/package.json
npm@types/bun1.4.2packages/runtime/package.json
npm@usepipr/sdk0.9.1packages/runtime/package.json
npmage-encryption0.3.0packages/runtime/package.json
npmfflate0.8.3packages/runtime/package.json
npmlodash-es4.18.1packages/runtime/package.json
npmpicomatch4.0.5packages/runtime/package.json
npmts-pattern5.9.0packages/runtime/package.json
npmtypescript6npm:typescript@6.0.3packages/runtime/package.json
npmzod4.4.3packages/runtime/package.json
npmzod4.4.3packages/sdk/package.json
All dependencies 66

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

RegistryPackageVersionRelation
npm@actions/core3.0.1direct
npm@earendil-works/chord1.0.4direct
npm@earendil-works/pi-ai1.0.4direct
npm@earendil-works/pi-durable1.0.4direct
npm@octokit/rest22.0.1direct
npm@opentelemetry/api1.9.1direct
npm@opentelemetry/exporter-logs-otlp-proto0.220.0direct
npm@opentelemetry/exporter-metrics-otlp-proto0.220.0direct
npm@opentelemetry/exporter-trace-otlp-proto0.220.0direct
npm@opentelemetry/resources2.9.0direct
npm@opentelemetry/sdk-logs0.220.0direct
npm@opentelemetry/sdk-metrics2.9.0direct
npm@opentelemetry/sdk-trace-base2.9.0direct
npm@opentelemetry/semantic-conventions1.43.0direct
npm@types/bun1.3.14direct
npm@types/bun1.4.2direct
npm@types/buncatalog:direct
npm@usepipr/runtime0.9.1direct
npm@usepipr/sdk0.9.1direct
npmage-encryption0.3.0direct
npmcommander15.0.0direct
npmfflate0.8.3direct
npmlodash-es4.18.1direct
npmpicomatch4.0.5direct
npmts-pattern5.9.0direct
npmzod4.4.3direct
npm@biomejs/biome2.5.15indirect
npm@fontsource-variable/jetbrains-mono5.3.0indirect
npm@fontsource-variable/roboto-mono5.3.0indirect
npm@hugeicons/core-free-icons4.2.3indirect
npm@hugeicons/react1.1.9indirect
npm@orama/orama3.1.18indirect
npm@playwright/test1.62.0indirect
npm@tailwindcss/vite4.3.3indirect
npm@takumi-rs/image-response2.5.0indirect
npm@tanstack/react-router1.170.18indirect
npm@tanstack/react-start1.168.32indirect
npm@tanstack/router-cli1.167.21indirect
npm@tanstack/start-static-server-functions1.167.19indirect
npm@types/lodash-es4.17.12indirect
npm@types/mdx2.0.14indirect
npm@types/node26.4.0indirect
npm@types/nodecatalog:indirect
npm@types/picomatch4.0.3indirect
npm@types/react19.2.17indirect
npm@types/react-dom19.2.3indirect
npm@vitejs/plugin-react6.0.4indirect
npmcopy-to-clipboard4.0.2indirect
npmdependency-cruiser18.5.0indirect
npmevalite0.19.0indirect
npmfallow3.31.0indirect
npmfumadocs-core16.12.1indirect
npmfumadocs-mdx15.2.0indirect
npmfumadocs-twoslash3.3.0indirect
npmfumadocs-typescript5.3.0indirect
npmfumadocs-ui16.12.1indirect
npmhappy-dom20.11.1indirect
npmnitro3.0.260610-betaindirect
npmreact19.2.8indirect
npmreact-dom19.2.8indirect
npmtailwindcss4.3.3indirect
npmtsdown0.23.0indirect
npmturbo2.11.7indirect
npmtypescript6.0.3indirect
npmtypescriptcatalog:indirect
npmvite8.1.5indirect
Dependency advisories 0

Installing npm:@usepipr/cli@0.9.1 pulls in 173 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.