Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-23 23:41 UTC

airomhq / airom

Open-source AI Bill of Materials (AIBOM) scanner: inventories AI models, datasets, prompts, embeddings, vector DBs & RAG pipelines across code, containers & Kubernetes — with file:line evidence, load-time risk detection (poisoned pickle / Keras Lambda / unsafe torch.load) and NIST AI RMF / OWASP compliance mapping. CycloneDX · SARIF · JSON.

Go · MDXApache-2.0★ 8 stars⑂ 2 forkssince Jul 2026View on GitHub ↗
KindCommand-line toolhow this is determined

airomhq/airom holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Security (100/100) and lowest on Sustainability & Governance (41/100). It was last updated today. 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

airomhqOrganization
0 followers2 public repossince Jul 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/airomhq/airomv0.1.9-80 days ago

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0.7/36Commit cadence1/52 weeks with commits
16.3/18Commit volume64 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year64
human_commit_share1
days_since_last_push0
active_weeks_last_year1

Release discipline

100Exceptional
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~0.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv0.1.9
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0.8

Community & Adoption

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

50Moderate · 17% of overall
How it's scored
13.7/60Stars8 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars8
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

41Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.3/22.5Commit distributiontop contributor authored 99% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.986
How it's scored
0/42Issue resolutionno issues or no data
7.5/30PR acceptance1/4 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs3
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of airomhq
3.5/25Track record2 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginairomhq
public_repos2
account_age_days6
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 0 days ago
20/20Version history8 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/airomhq/airom
ecosystemsgo
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

87Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
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/10Topics20 topics
10/10Wiki
Inputs used
topicsai-governance, ai-security, aibom, cyclonedx, golang, mlops, sarif, sbom, supply-chain-security, ai-bill-of-materials, compliance, devsecops, eu-ai-act, llm-security, ml-security, mlsecops, model-scanning, nist-ai-rmf, owasp, vulnerability-scanner
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?

100Exceptional · 16% of overall

Security posture

100Exceptional
How it's scored
30/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
20/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesgo.sum
manifestsgo.mod
has_codeql_workflowyes
has_security_policyyes
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.

77Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history71 of 72 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.986
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.golangci.yml
11/11Static type checkingsdk/python/src/airom/py.typed
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice70 of the last 72 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configssdk/python/src/airom/py.typed
agent_commit_share0.972
toolchain_manifestsgo.mod, internal/detectors/manifest/testdata/cargo/Cargo.toml, internal/detectors/manifest/testdata/gomod/go.mod, internal/detectors/manifest/testdata/gradle/build.gradle, internal/detectors/manifest/testdata/gradle/build.gradle.kts, internal/detectors/manifest/testdata/maven/pom.xml, internal/detectors/manifest/testdata/nuget/sample.csproj, internal/e2e/testdata/fixtures/go-openai/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/299 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes35,839
source_files_sampled299
oversized_source_files0

Key facts

8GitHub stars
2contributors
64commits, last 12 months
0days since last push
8releases
1bus factor
0open issues
Gopackage 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
  • OpenSSF Scorecard did not return a usable result (2026/07/23 23:40:47 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
1Releases

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.

111222212026-072026-072026-07
Major 0Minor 0Patch 1
Direct dependencies 16
RegistryPackageVersion constraintManifest
Gogithub.com/CycloneDX/cyclonedx-gov0.11.0go.mod
Gogithub.com/bmatcuk/doublestar/v4v4.10.0go.mod
Gogithub.com/charlievieth/fastwalkv1.0.14go.mod
Gogithub.com/cloudflare/ahocorasickv0.0.0-20240916140611-054963ec9396go.mod
Gogithub.com/go-git/go-git/v5v5.19.1go.mod
Gogithub.com/knadh/koanf/parsers/yamlv1.1.0go.mod
Gogithub.com/knadh/koanf/providers/filev1.2.1go.mod
Gogithub.com/knadh/koanf/providers/posflagv1.0.1go.mod
Gogithub.com/knadh/koanf/v2v2.3.5go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/pflagv1.0.10go.mod
Gogithub.com/zeebo/xxh3v1.1.0go.mod
Gogolang.org/x/modv0.38.0go.mod
Gogolang.org/x/syncv0.22.0go.mod
Gogolang.org/x/toolsv0.48.0go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
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.27.0 — full methodology · metrics wiki.

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