Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 20:41 UTC

nevenincs / vaultspec-core

Decision-driven harness for coding agents, and humans.

PythonMIT★ 2 stars⑂ 1 forksince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryMCP serverNetwork servicehow this is determined

nevenincs/vaultspec-core holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (34/100). It was last updated today. A single contributor accounts for most of its recent work.

78
overall / 100
Good

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.

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

Ownership

NevePersonal account
35 followers14 public repossince Mar 2015Neve

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
PyPIvaultspec-core0.2.15,889694 days agoacpadrai-assisteddecision-driven-developmentgovernancemcp

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
20.8/36Commit cadence — 30/52 weeks with commits
18/18Commit volume — 1,676 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,676
human_commit_share0.96
days_since_last_push0
active_weeks_last_year30
How it's scored
27/27Ships releases — 75 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~1.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count75
latest_release_tagvaultspec-core-v0.2.1
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases1.3

Community & Adoption

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

34At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars2
watchers1
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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
50.3/80Monthly downloads — 5,889 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesvaultspec-core
dependents—
ecosystemspypi
total_downloads—
monthly_downloads5,889
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.7/22.5Commit distribution — top contributor authored 92% of commits
4.1/13.5Contributor breadth — 3 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.925
How it's scored
41.8/42Issue resolution — 100% of issues closed
29.1/30PR acceptance — 331/341 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/24 approved changesets -- score normalized to 0
Inputs used
merged_prs331
open_issues1
closed_issues188
prs_merged_7d8
prs_decided_7d8
prs_merged_30d58
prs_decided_30d58
issue_closed_ratio0.995
closed_unmerged_prs10
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.2/25Owner reach — 35 followers of nevenincs
20.6/25Track record — 14 public repos, account ~11 yr old
Inputs used
followers35
owner_typeUser
is_verified—
owner_loginnevenincs
public_repos14
account_age_days4,213
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 pypi
35/35Publish recency — latest publish 4 days ago
20/20Version history — 69 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesvaultspec-core
ecosystemspypi
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://neve.md/vaultspec
10/10Repository description
10/10Topics — 19 topics
0/10Wiki
Inputs used
topicsadr, agent, agent-harness, agentic-coding, agents, agentskills, architecture-decision-record, architecture-decision-records, claude, claude-code, claude-skills, codex, framework, obsidian, skills, spec-driven-development, superpowers, vault, vibecoding
has_wikino
homepagehttps://neve.md/vaultspec
docs_sitehttps://neve.md/vaultspec
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
6/7.5Binary-Artifacts — binaries present in source code
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 3 out of 3 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/24 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 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): Packaging. 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_packages41
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:vaultspec-core@0.2.1 runtime dependency closure — what installing the published package pulls in — 41 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)
40/40Legible commit history — 84 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.875
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — justfile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.pylint])
11/11Static type checking — src/vaultspec_core/py.typed
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/vaultspec_core/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/vaultspec_core/py.typed)
54.7/55Manageable file sizes — 3/648 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes70,824
source_files_sampled648
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

2GitHub stars
3contributors
1,676commits, last 12 months
0days since last push
75releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

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-15 20:41 UTC

8Binary-Artifactsbinaries present in source code
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests3 out of 3 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/24 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
PyPIPyYAML>=6.0.3pyproject.toml
PyPImcp>=2.0.0pyproject.toml
PyPInetworkx>=3.6pyproject.toml
PyPIphart>=0.5.0pyproject.toml
PyPIpydantic>=2.12.5pyproject.toml
PyPIrich>=14.3.2pyproject.toml
PyPIruamel.yaml>=0.18pyproject.toml
PyPIrustworkx>=0.18.0pyproject.toml
PyPIsse-starlette>=3.2.0pyproject.toml
PyPIstarlette>=0.52.1pyproject.toml
PyPItyper>=0.12.0pyproject.toml
PyPIuvicorn>=0.41.0pyproject.toml
All dependencies 144

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

RegistryPackageVersionRelation
PyPImcp2.2.0direct
PyPInetworkx3.6.1direct
PyPIphart1.1.4direct
PyPIphart2.1.0direct
PyPIpydantic2.13.5direct
PyPIpyyaml6.0.3direct
PyPIrich15.0.0direct
PyPIruamel-yaml0.19.1direct
PyPIrustworkx0.18.1direct
PyPIsse-starlette3.4.11direct
PyPIstarlette1.6.0direct
PyPItyper0.27.2direct
PyPIuvicorn0.52.4direct
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIanyio4.15.1indirect
PyPIapplication-file-scanner0.6.4indirect
PyPIapplication-properties0.9.3indirect
PyPIastroid4.0.4indirect
PyPIattrs26.1.0indirect
PyPIbandit1.9.4indirect
PyPIbasedpyright1.40.1indirect
PyPIcargo-zigbuild0.23.4indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcolumnar1.4.1indirect
PyPIcomplexipy8.0.1indirect
PyPIcryptography50.0.1indirect
PyPIcuda-bindings13.4.1indirect
PyPIcuda-pathfinder1.8.1indirect
PyPIcuda-toolkit13.0.3.0indirect
PyPIdeptry0.25.1indirect
PyPIdill0.4.1indirect
PyPIexecnet2.1.2indirect
PyPIfilelock3.32.6indirect
PyPIfsspec2026.7.0indirect
PyPIgrpcio1.83.1indirect
PyPIh110.16.0indirect
PyPIh24.4.1indirect
PyPIhf-xet1.6.0indirect
PyPIhpack4.2.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpcore22.12.0indirect
PyPIhttpx0.28.1indirect
PyPIhttpx22.12.0indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIhuggingface-hub1.31.0indirect
PyPIhyperframe6.1.0indirect
PyPIidentify2.6.19indirect
PyPIidna3.19indirect
PyPIiniconfig2.3.0indirect
PyPIisort9.0.1indirect
PyPIjinja23.1.6indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIlinkify-it-py2.2.0indirect
PyPImando0.7.1indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImccabe0.7.0indirect
PyPImcp-types2.2.0indirect
PyPImdformat1.0.0indirect
PyPImdformat-frontmatter2.1.2indirect
PyPImdformat-gfm1.0.0indirect
PyPImdformat-gfm-alerts2.1.0indirect
PyPImdit-py-plugins0.6.1indirect
PyPImdurl0.1.2indirect
PyPImpmath1.3.0indirect
PyPImypy-extensions1.1.0indirect
PyPInodejs-wheel-binaries24.19.0indirect
PyPInumpy2.5.3indirect
PyPInvidia-cublas13.1.1.3indirect
PyPInvidia-cuda-cupti13.0.85indirect
PyPInvidia-cuda-nvrtc13.0.88indirect
PyPInvidia-cuda-runtime13.0.96indirect
PyPInvidia-cudnn-cu139.24.0.43indirect
PyPInvidia-cufft12.0.0.61indirect
PyPInvidia-cufile1.15.1.6indirect
PyPInvidia-curand10.4.0.35indirect
PyPInvidia-cusolver12.0.4.66indirect
PyPInvidia-cusparse12.6.3.3indirect
PyPInvidia-cusparselt-cu130.8.1indirect
PyPInvidia-nccl-cu132.30.7indirect
PyPInvidia-nvjitlink13.4.52indirect
PyPInvidia-nvshmem-cu133.4.5indirect
PyPInvidia-nvtx13.0.85indirect
PyPIopentelemetry-api1.44.0indirect
PyPIpackaging26.3indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.8indirect
PyPIpluggy1.6.0indirect
PyPIportalocker3.2.0indirect
PyPIprotobuf7.36.1indirect
PyPIpsutil7.2.2indirect
PyPIpy-walk0.3.3indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.5indirect
PyPIpygments2.21.0indirect
PyPIpyjson52.0.1indirect
PyPIpyjwt2.13.0indirect
PyPIpylint4.0.8indirect
PyPIpymarkdownlnt0.9.39indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-timeout2.4.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dotenv1.2.3indirect
PyPIpython-multipart0.0.32indirect
PyPIpywin32312indirect
PyPIqdrant-client1.19.0indirect
PyPIradon6.0.1indirect
PyPIreferencing0.37.0indirect
PyPIrequirements-parser0.13.1indirect
PyPIrpds-py2026.6.3indirect
PyPIruff0.16.7indirect
PyPIsetuptools84.0.0indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsly0.5indirect
PyPIstevedore5.9.1indirect
PyPIsympy1.14.0indirect
PyPItextual8.2.8indirect
PyPItomli2.4.1indirect
PyPItomlkit0.15.1indirect
PyPItoolz1.1.0indirect
PyPItorch2.14.0indirect
PyPItorch2.14.0+cu130indirect
PyPItqdm4.70.0indirect
PyPItree-sitter0.26.0indirect
PyPItree-sitter-language-pack1.6.1indirect
PyPItriton3.8.0indirect
PyPItruststore0.10.4indirect
PyPIty0.0.80indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib32.7.0indirect
PyPIvaultspec-core0.2.1indirect
PyPIvaultspec-rag0.4.25indirect
PyPIvulture2.16indirect
PyPIwatchfiles1.2.0indirect
PyPIwcwidth0.8.3indirect
PyPIziglang0.16.0indirect
Dependency advisories 0

Installing pypi:vaultspec-core@0.2.1 pulls in 41 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.