Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 03:22 UTC

Sting25 / ai-coding-rules-scaffold

Two-layer enforcement (pre-commit hook + CI mirror) for small teams using AI agents. Catches debug leaks, file growth, secrets, and forbidden patterns before they merge.

ShellMIT★ 4 stars⑂ 0 forkssince Apr 2026View on GitHub ↗

Sting25/ai-coding-rules-scaffold holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Vitality (75/100) and lowest on AI Readiness (26/100). It was last updated 15 days ago. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

Christopher ChadwickPersonal account
5 followers3 public repossince Feb 2010

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
npmai-coding-rules-scaffold0.10.0296115 days agopre-commitgit-hookslintingsecretssecret-scanningsecurityguardrailsscaffoldciai-codingcode-review

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
28.8/36Push recencylast push 15 days ago
6.2/36Commit cadence9/52 weeks with commits
18/18Commit volume202 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year202
human_commit_share
days_since_last_push15
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases14 releases published
36/36Release recencylatest release 15 days ago
27/27Release cadencea release every ~6.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tagv0.10.0
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases6.6

Community & Adoption

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

31At Risk · 17% of overall
How it's scored
7.7/60Stars4 stars
0/25Forks0 forks
0/15Watchers0 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.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
33/80Monthly downloads296 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesai-coding-rules-scaffold
dependents
ecosystemsnpm
total_downloads
monthly_downloads296
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.9/22.5Commit distributiontop contributor authored 96% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.96
How it's scored
0/42Issue resolutionno issues or no data
29.5/30PR acceptance55/56 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs55
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs1
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
5.6/25Owner reach5 followers of Sting25
16.4/25Track record3 public repos, account ~16 yr old
Inputs used
followers5
owner_typeUser
is_verified
owner_loginSting25
public_repos3
account_age_days6,002
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 15 days ago
4/20Version history1 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesai-coding-rules-scaffold
ecosystemsnpm
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsagents-md, ai-agents, coding-standards, eslint, linting, pre-commit-hooks, ruff, claude-code, cursor
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestspackage.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeShell without a type-check config
55/55Manageable file sizes0/2 source files over 60KB
Inputs used
primary_languageShell
largest_source_bytes3,317
source_files_sampled2
oversized_source_files0

Key facts

4GitHub stars
3contributors
202commits, last 12 months
15days since last push
14releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

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

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.11.0 — full methodology · metrics wiki.

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