Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 08:34 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.

GoApache-2.0★ 15 stars⑂ 4 forkssince Jul 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

airomhq/airom holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Security (100/100) and lowest on Sustainability & Governance (52/100). It was last updated 13 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

airomhqOrganization
0 followers4 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.4.4-2619 days ago

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
28.8/36Push recency — last push 13 days ago
4.8/36Commit cadence — 7/52 weeks with commits
18/18Commit volume — 155 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year155
human_commit_share0.97
days_since_last_push13
active_weeks_last_year7

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 26 releases published
36/36Release recency — latest release 19 days ago
27/27Release cadence — a release every ~2.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tagv0.4.4
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases2.6

Community & Adoption

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

55Moderate · 17% of overall
How it's scored
18.6/60Stars — 15 stars
4/25Forks — 4 forks
0/15Watchers — 0 watchers
Inputs used
forks4
stars15
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, goreportcard.com, pkg.go.dev, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.5/22.5Commit distribution — top contributor authored 98% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.98
How it's scored
35/42Issue resolution — 83% of issues closed
18/30PR acceptance — 9/15 decided PRs merged
10.4/13Newcomer PR acceptance — 4/5 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs9
open_issues1
closed_issues5
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.833
closed_unmerged_prs6
first_time_authors_30d3
first_time_prs_merged_30d4
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of airomhq
5.4/25Track record — 4 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginairomhq
public_repos4
account_age_days58

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 19 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/airomhq/airom
ecosystemsgo
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

87Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml
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

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 20 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 lockfiles — published library — lockfiles are an application concern, not expected
20/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesPipfile.lock, go.sum, package-lock.json, pnpm-lock.yaml, poetry.lock, uv.lock, yarn.lock
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.

79Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 97 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .golangci.yml
11/11Static type checking — sdk/python/src/airom/py.typed
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 95 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesPipfile.lock, go.sum, package-lock.json, pnpm-lock.yaml, poetry.lock, uv.lock, yarn.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configssdk/python/src/airom/py.typed
agent_commit_share0.95
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.03
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/396 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes40,754
source_files_sampled396
oversized_source_files0

Key facts

15GitHub stars
3contributors
155commits, last 12 months
13days since last push
26releases
1bus factor
1open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 15 stars today.
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/13 08:32:41 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 8 ★ / 4 ⇿
8Stars
4Forks
19Releases

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.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

024688472026-072026-082026-08
Major 0Minor 3Patch 16
Direct dependencies 17
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.2go.mod
Gogithub.com/knadh/koanf/parsers/yamlv1.1.1go.mod
Gogithub.com/knadh/koanf/providers/filev1.2.1go.mod
Gogithub.com/knadh/koanf/providers/posflagv1.0.2go.mod
Gogithub.com/knadh/koanf/v2v2.3.6go.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.40.0go.mod
Gogolang.org/x/syncv0.22.0go.mod
Gogolang.org/x/termv0.45.0go.mod
Gogolang.org/x/toolsv0.49.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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go.