Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 01:42 UTC

AsiaOstrich / universal-dev-standards

Universal, language-agnostic development standards for software projects. Includes coding standards, git workflows, testing guidelines, documentation structure, and AI collaboration rules.

JavaScriptCustom license★ 73 stars⑂ 13 forkssince Dec 2025View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

AsiaOstrich/universal-dev-standards holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Sustainability & Governance (50/100). It was last updated 2 days ago. 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

AsiaOstrichPersonal account
10 followers13 public repossince Jun 2016

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
npmuniversal-dev-standards6.8.02,00816225 days agodocumentationstandardsclideveloper-toolsbest-practices

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 1,332 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,332
human_commit_share0.94
days_since_last_push2
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 25 days ago
27/27Release cadence — a release every ~1.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv6.8.0
releases_from_tagsno
days_since_latest_release25
mean_days_between_releases1.1
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?

54Moderate · 17% of overall
How it's scored
30.1/60Stars — 73 stars
9/25Forks — 13 forks
0/15Watchers — 1 watchers
Inputs used
forks13
stars73
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
44/80Monthly downloads — 2,008 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesuniversal-dev-standards
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,008
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?

50Moderate · 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
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
39.1/42Issue resolution — 93% of issues closed
22.2/30PR acceptance — 88/119 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs88
open_issues4
closed_issues53
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.93
closed_unmerged_prs31
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
7.5/25Owner reach — 10 followers of AsiaOstrich
20.3/25Track record — 13 public repos, account ~10 yr old
Inputs used
followers10
owner_typeUser
is_verified—
owner_loginAsiaOstrich
public_repos13
account_age_days3,751
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 25 days ago
20/20Version history — 162 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesuniversal-dev-standards
ecosystemsnpm
any_deprecatedno
min_days_since_publish25

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 18 topics
0/10Wiki
Inputs used
topicsai-collaboration, best-practices, claude-code, code-review, coding-standards, commit-conventions, conventional-commits, developer-tools, development-standards, devops, documentation, git-workflow, quality-assurance, semantic-versioning, skills, software-engineering, spec-driven-development, testing-standards
has_wikino
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?

58Moderate · 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
0/2.5CI-Tests — no data
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/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): CI-Tests, 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_packages45
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:universal-dev-standards@6.8.0 runtime dependency closure — what installing the published package pulls in — 45 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md, integrations/aider/AGENTS.md, integrations/claude-code/CLAUDE.md, integrations/cline/.clinerules, integrations/codex/AGENTS.md, integrations/continue-dev/AGENTS.md, integrations/cursor/.cursorrules, integrations/gemini-cli/GEMINI.md, integrations/google-antigravity/AGENTS.md, integrations/opencode/AGENTS.md, integrations/openspec/AGENTS.md, integrations/roo-code/.clinerules, integrations/spec-kit/AGENTS.md, integrations/windsurf/.windsurfrules, locales/zh-CN/CLAUDE.md, locales/zh-CN/integrations/codex/AGENTS.md, locales/zh-CN/integrations/gemini-cli/GEMINI.md, locales/zh-CN/integrations/google-antigravity/AGENTS.md, locales/zh-CN/integrations/opencode/AGENTS.md, locales/zh-CN/integrations/openspec/AGENTS.md, locales/zh-CN/integrations/spec-kit/AGENTS.md, locales/zh-TW/CLAUDE.md, locales/zh-TW/integrations/codex/AGENTS.md, locales/zh-TW/integrations/gemini-cli/GEMINI.md, locales/zh-TW/integrations/google-antigravity/AGENTS.md, locales/zh-TW/integrations/opencode/AGENTS.md, locales/zh-TW/integrations/openspec/AGENTS.md, locales/zh-TW/integrations/spec-kit/AGENTS.md, skills/tools/cline/.clinerules, skills/tools/cursor/.cursorrules, skills/tools/windsurf/.windsurfrules
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 94 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md, integrations/aider/AGENTS.md, integrations/claude-code/CLAUDE.md, integrations/cline/.clinerules, integrations/codex/AGENTS.md, integrations/continue-dev/AGENTS.md, integrations/cursor/.cursorrules, integrations/gemini-cli/GEMINI.md, integrations/google-antigravity/AGENTS.md, integrations/opencode/AGENTS.md, integrations/openspec/AGENTS.md, integrations/roo-code/.clinerules, integrations/spec-kit/AGENTS.md, integrations/windsurf/.windsurfrules, locales/zh-CN/CLAUDE.md, locales/zh-CN/integrations/codex/AGENTS.md, locales/zh-CN/integrations/gemini-cli/GEMINI.md, locales/zh-CN/integrations/google-antigravity/AGENTS.md, locales/zh-CN/integrations/opencode/AGENTS.md, locales/zh-CN/integrations/openspec/AGENTS.md, locales/zh-CN/integrations/spec-kit/AGENTS.md, locales/zh-TW/CLAUDE.md, locales/zh-TW/integrations/codex/AGENTS.md, locales/zh-TW/integrations/gemini-cli/GEMINI.md, locales/zh-TW/integrations/google-antigravity/AGENTS.md, locales/zh-TW/integrations/opencode/AGENTS.md, locales/zh-TW/integrations/openspec/AGENTS.md, locales/zh-TW/integrations/spec-kit/AGENTS.md, skills/tools/cline/.clinerules, skills/tools/cursor/.cursorrules, skills/tools/windsurf/.windsurfrules
agent_instruction_max_bytes41,107
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 92 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 6 of the last 100 commits are automated dependency updates
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.92
toolchain_manifests—
dependency_bot_commit_share0.06
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.1/55Manageable file sizes — 6/383 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes160,080
source_files_sampled383
oversized_source_files6
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 — examples, recipes
Inputs used
example_dirsexamples, recipes
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

73GitHub stars
1contributors
1,332commits, last 12 months
2days since last push
100releases
1bus factor
4open 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 ★ / 13 ⇿
0Stars
13Forks
92Releases

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.

03581013151322025-122026-042026-08
Major 3Minor 21Patch 30
OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-14 01:42 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
npm@inquirer/prompts^8.4.2cli/package.json
npmchalk^6.0.0cli/package.json
npmcommander^15.0.0cli/package.json
npmjs-yaml^5.2.1cli/package.json
npmora^9.4.0cli/package.json
npmsemver^7.8.5cli/package.json
npm@asiaostrich/telemetry-client^0.1.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 0

Installing npm:universal-dev-standards@6.8.0 pulls in 45 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.