Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 00:20 UTC

manojlds / drs

Workflow-first AI code maintenance for reviews, changelogs, docs, and repository upkeep.

TypeScriptApache-2.0★ 1 star⑂ 2 forkssince Jan 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

manojlds/drs holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (33/100). It was last updated 46 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ManojPersonal account
164 followers171 public repossince Jan 2010@Avalara

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 publishTags
npm@diff-review-system/drs5.0.03,5111851 days agogitlabgithubcode-reviewpidiff-reviewmerge-requestpull-requestcode-analysisstatic-analysis

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
18/36Push recency — last push 46 days ago
15.9/36Commit cadence — 23/52 weeks with commits
18/18Commit volume — 718 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_year718
human_commit_share0.97
days_since_last_push46
active_weeks_last_year23
How it's scored
27/27Ships releases — 5 releases published
27/36Release recency — latest release 131 days ago
27/27Release cadence — a release every ~16.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count5
latest_release_tagv3.3.1
releases_from_tagsno
days_since_latest_release131
mean_days_between_releases16.8
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?

33At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars1
watchers0
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
47.3/80Monthly downloads — 3,511 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@diff-review-system/drs
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,511
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.3/22.5Commit distribution — top contributor authored 81% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.809
How it's scored
0/42Issue resolution — no issues or no data
27.2/30PR acceptance — 185/204 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/15 approved changesets -- score normalized to 0
Inputs used
merged_prs185
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs19
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
15.9/25Owner reach — 164 followers of manojlds
25/25Track record — 171 public repos, account ~16 yr old
Inputs used
followers164
owner_typeUser
is_verified—
owner_loginmanojlds
public_repos171
account_age_days6,071
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 51 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@diff-review-system/drs
ecosystemsnpm
any_deprecatedno
min_days_since_publish51

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

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

Security

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

39Weak · 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.5/2.5CI-Tests — 10 out of 10 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/15 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — 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 — 30 commit(s) and 0 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
0/7.5Vulnerabilities — 29 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.1
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
6.6/25Indirect dependencies free of known advisories — 4 affected: decode-uri-component 0.2.2 (high 7.5), undici 8.5.0 (high 7.4), vite 5.4.21 (high 7.5), +1 more
30.3/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 579 days ago
Inputs used
sourceosv
advisories10
affected_packages4
assessed_packages552
unassessed_packages0
affected_by_severityhigh 3, moderate 1
direct_affected_packages0
Matched the npm:@diff-review-system/drs@5.0.0 runtime dependency closure — what installing the published package pulls in — 552 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.

89Excellent · 4% of overall
How it's scored
45/45Agent instructions — .drs/agents/task/changelog-updater/agent.md, AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://manojlds.github.io/drs/llms.txt)
40/40Legible commit history — 94 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://manojlds.github.io/drs/llms.txt
legible_history_share0.969
agent_instruction_files.drs/agents/task/changelog-updater/agent.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes1,770
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
11/11Lint / format config — .eslintrc.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
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_filesmise.toml
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.4/55Manageable file sizes — 2/192 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes181,505
source_files_sampled192
oversized_source_files2

Key facts

1GitHub stars
2contributors
718commits, last 12 months
46days since last push
5releases
1bus factor
0open 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

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-13 00:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests10 out of 10 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/15 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update 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
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
0Vulnerabilities29 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
npm@earendil-works/pi-coding-agent^0.82.1package.json
npm@gitbeaker/node^35.8.1package.json
npm@octokit/rest^21.0.0package.json
npm@sinclair/typebox^0.34.49package.json
npm@temporalio/activity^1.20.3package.json
npm@temporalio/client^1.20.3package.json
npm@temporalio/worker^1.20.3package.json
npm@temporalio/workflow^1.20.3package.json
npmajv^8.20.0package.json
npmchalk^5.3.0package.json
npmcommander^12.0.0package.json
npmdotenv^16.0.0package.json
npmmarkdown-it^14.3.0package.json
npmminimatch^10.2.5package.json
npmsimple-git^3.36.0package.json
npmvitepress^1.6.4package.json
npmyaml^2.9.0package.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 4

Installing npm:@diff-review-system/drs@5.0.0 pulls in 552 packages, direct and transitive: 4 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
decode-uri-component0.2.2indirecthigh10.5.0
undici8.5.0indirecthigh58.9.0
vite5.4.21indirecthigh38.0.16
esbuild0.21.5indirectmoderate10.25.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

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.