Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-28 23:03 UTC

opena2a-org / opena2a

One scan for AI risk. `opena2a review` checks an AI project across credentials, shadow agents, MCP servers, and dependencies, returns a score, and routes each finding to the tool that fixes it. Open source.

TypeScriptApache-2.0★ 21 stars⑂ 8 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

opena2a-org/opena2a holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on Community & Adoption (53/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

opena2a.orgOrganization
26 followers23 public repossince Apr 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmopena2a-cli0.10.138857753 days agoaiagentsecurityscannermcpcredentialsidentity
npm@opena2a/cli-ui0.5.21,5367112 days ago—
npm@opena2a/shared0.1.21,8853159 days ago—
npm@opena2a/aim-core0.2.03,2374159 days agoaiagentidentityed25519securityaimopena2a
npm@opena2a/telemetry0.3.02,1315127 days ago—
npm@opena2a/atx-verify0.4.01,672583 days ago—
npm@opena2a/check-core0.3.02,0614109 days ago—
npm@opena2a/contribute0.3.03,029433 days ago—

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 503 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_year503
human_commit_share0.74
days_since_last_push0
active_weeks_last_year28

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 72 releases published
36/36Release recency — latest release 33 days ago
27/27Release cadence — a release every ~8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count72
latest_release_tagcontribute-v0.3.0
releases_from_tagsno
days_since_latest_release33
mean_days_between_releases8
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?

53Moderate · 17% of overall
How it's scored
21.1/60Stars — 21 stars
7/25Forks — 8 forks
0/15Watchers — 2 watchers
Inputs used
forks8
stars21
watchers2
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)
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_servicesshields.io
has_pull_request_templateno
How it's scored
56.2/80Monthly downloads — 16,436 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesopena2a-cli, @opena2a/cli-ui, @opena2a/shared, @opena2a/aim-core, @opena2a/telemetry, @opena2a/atx-verify, @opena2a/check-core, @opena2a/contribute
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads16,436
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?

55Moderate · 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
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.998
How it's scored
33.1/42Issue resolution — 79% of issues closed
28.2/30PR acceptance — 262/279 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs262
open_issues16
closed_issues59
prs_merged_7d10
prs_decided_7d12
prs_merged_30d11
prs_decided_30d15
issue_closed_ratio0.787
closed_unmerged_prs17
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
10.3/25Owner reach — 26 followers of opena2a-org
12.9/25Track record — 23 public repos, account ~1 yr old
Inputs used
followers26
owner_typeOrganization
is_verifiedno
owner_loginopena2a-org
public_repos23
account_age_days527

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 33 days ago
20/20Version history — 77 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesopena2a-cli, @opena2a/cli-ui, @opena2a/shared, @opena2a/aim-core, @opena2a/telemetry, @opena2a/atx-verify, @opena2a/check-core, @opena2a/contribute
ecosystemsnpm
any_deprecatedno
min_days_since_publish33

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://opena2a.org
10/10Repository description
10/10Topics — 14 topics
10/10Wiki
Inputs used
topicsagent-security, ai-agents, ai-security, claude-code, compliance, copilot, credential-protection, cursor, llm-security, mcp, open-source, security-tools, vulnerability-scanner, tool
has_wikiyes
homepagehttps://opena2a.org
docs_sitehttps://opena2a.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 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
2.5/2.5CI-Tests — 30 out of 30 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/10 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 — 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5
Excluded from scoring (no data or not applicable): 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_packages174
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:opena2a-cli@0.10.13 runtime dependency closure — what installing the published package pulls in — 174 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.

70Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://opena2a.org/llms.txt)
40/40Legible commit history — 73 of 74 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://opena2a.org/llms.txt
legible_history_share0.986
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — packages/ai-classifier/tsconfig.json, packages/aim-core/tsconfig.json, packages/atx-verify/tsconfig.json, packages/check-core/tsconfig.json, packages/cli-ui/tsconfig.json, packages/cli/tsconfig.json, packages/contribute/tsconfig.json, packages/credential-patterns/tsconfig.json, packages/registry-client/tsconfig.json, packages/shared/tsconfig.json, packages/telemetry/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_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/ai-classifier/tsconfig.json, packages/aim-core/tsconfig.json, packages/atx-verify/tsconfig.json, packages/check-core/tsconfig.json, packages/cli-ui/tsconfig.json, packages/cli/tsconfig.json, packages/contribute/tsconfig.json, packages/credential-patterns/tsconfig.json, packages/registry-client/tsconfig.json, packages/shared/tsconfig.json, packages/telemetry/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.2/55Manageable file sizes — 6/413 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes86,765
source_files_sampled413
oversized_source_files6
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — demos, examples
Inputs used
example_dirsdemos, examples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

21GitHub stars
2contributors
503commits, last 12 months
0days since last push
72releases
1bus factor
16open 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 ★ / 8 ⇿
0Stars
8Forks
72Releases

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.

1234567712026-022026-062026-09
Major 0Minor 2Patch 33
OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-28 23:03 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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/10 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
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
npmjs-yaml^4.1.1packages/aim-core/package.json
npmtweetnacl^1.0.3packages/aim-core/package.json
npmcanonicalize2.1.0packages/atx-verify/package.json
npm@opena2a/registry-client0.1.0packages/check-core/package.json
npmchalk^5.3.0packages/cli-ui/package.json
npm@inquirer/prompts^7.0.0packages/cli/package.json
npm@opena2a/aicomply2.2.3packages/cli/package.json
npm@opena2a/cli-ui0.6.0packages/cli/package.json
npm@opena2a/contribute0.1.0packages/cli/package.json
npm@opena2a/credential-patterns0.1.3packages/cli/package.json
npm@opena2a/registry-client0.2.0packages/cli/package.json
npm@opena2a/shared0.1.2packages/cli/package.json
npm@opena2a/telemetry0.3.0packages/cli/package.json
npmai-trust^0.2.23packages/cli/package.json
npmcommander^13.1.0packages/cli/package.json
npmhackmyagent0.30.0packages/cli/package.json
npmsecretless-ai0.23.0packages/cli/package.json
npmtweetnacl^1.0.3packages/registry-client/package.json
npmzod^3.24.0packages/shared/package.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:opena2a-cli@0.10.13 pulls in 174 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.