Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 03:09 UTC

UKGovernmentBEIS / inspect_cyber

An Inspect extension for agentic cyber evaluations

PythonMIT★ 43 stars⑂ 10 forkssince Jan 2025View on GitHub ↗
KindPluginLibraryhow this is determined

UKGovernmentBEIS/inspect_cyber holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (84/100) and lowest on Vitality (37/100). It was last updated 122 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

291 followers115 public repossince May 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIinspect_cyber0.1.018,8802497 days ago

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 122 days ago
6.9/36Commit cadence — 10/52 weeks with commits
10.3/18Commit volume — 13 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year13
human_commit_share1
days_since_last_push122
active_weeks_last_year10
How it's scored
27/27Ships releases — 1 releases published
7.2/36Release recency — latest release 481 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.1.0
releases_from_tagsno
days_since_latest_release481
mean_days_between_releases—
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?

41Weak · 17% of overall
How it's scored
26.3/60Stars — 43 stars
8/25Forks — 10 forks
0/15Watchers — 0 watchers
Inputs used
forks10
stars43
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

64Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.4/22.5Commit distribution — top contributor authored 45% of commits
13.5/13.5Contributor breadth — 12 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.448
How it's scored
17.2/42Issue resolution — 41% of issues closed
26.2/30PR acceptance — 62/71 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 23/28 approved changesets -- score normalized to 8
Inputs used
merged_prs62
open_issues26
closed_issues18
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.409
closed_unmerged_prs9
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
17.7/25Owner reach — 291 followers of UKGovernmentBEIS
25/25Track record — 115 public repos, account ~10 yr old
Inputs used
followers291
owner_typeOrganization
is_verifiedno
owner_loginUKGovernmentBEIS
public_repos115
account_age_days3,817
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
14/35Publish recency — latest publish 497 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesinspect_cyber
ecosystemspypi
any_deprecatedno
min_days_since_publish497

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 18 out of 28 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://inspect.cyber.aisi.org.uk/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttp://inspect.cyber.aisi.org.uk/
docs_sitehttp://inspect.cyber.aisi.org.uk/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.5/2.5CI-Tests — 18 out of 28 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 23/28 approved changesets -- score normalized to 8
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 59 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): 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_packages79
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 pypi:inspect_cyber@0.1.0 runtime dependency closure — what installing the published package pulls in — 79 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
39.8/40Legible commit history — 50 of 67 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.746
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — src/inspect_cyber/py.typed
10/10Reproducible environment — lockfile
9/10Demonstrated agent practice — 3 of the last 67 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configssrc/inspect_cyber/py.typed
agent_commit_share0.045
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/inspect_cyber/py.typed)
55/55Manageable file sizes — 0/31 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes32,607
source_files_sampled31
oversized_source_files0

Key facts

43GitHub stars
12contributors
13commits, last 12 months
122days since last push
1releases
2bus factor
26open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 10 ⇿
0Stars
10Forks
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.

02468101012025-042025-112026-06
Major 0Minor 1Patch 0

Each point covers 2 days.

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-10-19 03:09 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests18 out of 28 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 23/28 approved changesets -- score normalized to 8
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities59 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIinspect-ai>=0.3.174,<0.4pyproject.toml
All dependencies 97

Full resolved dependency set from the GitHub dependency graph: 1 direct and 96 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIinspect-ai0.3.202direct
PyPIaioboto315.5.0indirect
PyPIaiobotocore2.25.1indirect
PyPIaiofiles25.1.0indirect
PyPIaiohappyeyeballs2.6.1indirect
PyPIaiohttp3.11.18indirect
PyPIaioitertools0.12.0indirect
PyPIaiosignal1.3.2indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.9.0indirect
PyPIasync-timeout5.0.1indirect
PyPIattrs25.3.0indirect
PyPIbeautifulsoup44.13.4indirect
PyPIboto31.40.61indirect
PyPIbotocore1.40.61indirect
PyPIcertifi2025.4.26indirect
PyPIcfgv3.4.0indirect
PyPIcharset-normalizer3.4.6indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIdebugpy1.8.14indirect
PyPIdistlib0.3.9indirect
PyPIdocstring-parser0.16indirect
PyPIexceptiongroup1.2.2indirect
PyPIfilelock3.18.0indirect
PyPIfrozenlist1.6.0indirect
PyPIfsspec2025.3.0indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIidentify2.6.10indirect
PyPIidna3.10indirect
PyPIijson3.3.0indirect
PyPIiniconfig2.1.0indirect
PyPIjmespath1.0.1indirect
PyPIjsonlines4.0.0indirect
PyPIjsonpatch1.33indirect
PyPIjsonpath-ng1.8.0indirect
PyPIjsonpointer3.0.0indirect
PyPIjsonref1.1.0indirect
PyPIjsonschema4.23.0indirect
PyPIjsonschema-specifications2025.4.1indirect
PyPIlinkify-it-py2.0.3indirect
PyPImarkdown-it-py3.0.0indirect
PyPImdit-py-plugins0.4.2indirect
PyPImdurl0.1.2indirect
PyPImmh35.1.0indirect
PyPImultidict6.4.3indirect
PyPInest-asyncio21.7.2indirect
PyPInodeenv1.9.1indirect
PyPInumpy2.2.5indirect
PyPIpackaging25.0indirect
PyPIpathlib-abc0.5.2indirect
PyPIplatformdirs4.3.7indirect
PyPIpluggy1.5.0indirect
PyPIpre-commit3.8.0indirect
PyPIpropcache0.3.1indirect
PyPIpsutil7.0.0indirect
PyPIpydantic2.12.5indirect
PyPIpydantic-core2.41.5indirect
PyPIpygments2.19.1indirect
PyPIpyright1.1.406indirect
PyPIpytest8.3.5indirect
PyPIpytest-asyncio0.23.8indirect
PyPIpytest-repeat0.9.4indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.1.0indirect
PyPIpyyaml6.0.2indirect
PyPIreferencing0.36.2indirect
PyPIregex2026.3.32indirect
PyPIrequests2.33.1indirect
PyPIrich13.9.4indirect
PyPIrpds-py0.24.0indirect
PyPIruff0.6.9indirect
PyPIs3fs2025.3.0indirect
PyPIs3transfer0.14.0indirect
PyPIsemver3.0.4indirect
PyPIshortuuid1.0.13indirect
PyPIsix1.17.0indirect
PyPIsniffio1.3.1indirect
PyPIsoupsieve2.7indirect
PyPItenacity9.1.2indirect
PyPItextual3.1.1indirect
PyPItiktoken0.12.0indirect
PyPItomli2.2.1indirect
PyPItypes-pyyaml6.0.12.20250402indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPIuc-micro-py1.0.3indirect
PyPIuniversal-pathlib0.3.10indirect
PyPIurllib32.4.0indirect
PyPIvirtualenv20.30.0indirect
PyPIwrapt1.17.2indirect
PyPIyarl1.20.0indirect
PyPIzipfile-zstd0.0.4indirect
PyPIzipp3.21.0indirect
PyPIzstandard0.25.0indirect
Dependency advisories 0

Installing pypi:inspect_cyber@0.1.0 pulls in 79 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 — PyPI.