Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 00:56 UTC

netresearch / t3x-nr-vault

Secure secrets management for TYPO3 with envelope encryption, access control, and audit logging

PHPGPL-2.0★ 2 stars⑂ 0 forkssince Dec 2025View on GitHub ↗

netresearch/t3x-nr-vault holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (89/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

40 followers278 public repossince Nov 2009

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

Package ecosystems

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
18.7/36Commit cadence27/52 weeks with commits
18/18Commit volume918 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year918
human_commit_share
days_since_last_push0
active_weeks_last_year27

Release discipline

98Exceptional
How it's scored
27/27Ships releases20 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~14.4 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count20
latest_release_tagv0.10.1
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases14.4

Community & Adoption

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

47Weak · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars2
watchers1
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 (GPL-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
How it's scored
55.2/80Monthly downloads13,813 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesnetresearch/nr-vault
dependents1
ecosystemspackagist
total_downloads35,437
monthly_downloads13,813
unverified_packages_excluded

Sustainability & Governance

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

69Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.2/22.5Commit distributiontop contributor authored 81% of commits
5.4/13.5Contributor breadth4 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.813
How it's scored
28/42Issue resolution67% of issues closed
28.5/30PR acceptance184/194 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs184
open_issues2
closed_issues4
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.667
closed_unmerged_prs10
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.6/25Owner reach40 followers of netresearch
25/25Track record278 public repos, account ~16 yr old
Inputs used
followers40
owner_typeOrganization
is_verified
owner_loginnetresearch
public_repos278
account_age_days6,091
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 packagist
35/35Publish recencylatest publish 12 days ago
20/20Version history20 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesnetresearch/nr-vault
ecosystemspackagist
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicstypo3-extension
has_wikino
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?

83Excellent · 16% of overall

Security posture

83Excellent
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
1.8/2.5CII-Best-Practicesbadge detected: Silver
7.5/7.5Code-Reviewall changesets reviewed
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate8.3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. 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.

75Good · 4% of overall
How it's scored
45/45Agent instructions.ddev/AGENTS.md, .ddev/CLAUDE.md, .ddev/GEMINI.md, .github/workflows/AGENTS.md, .github/workflows/CLAUDE.md, .github/workflows/GEMINI.md, AGENTS.md, CLAUDE.md, Classes/AGENTS.md, Classes/CLAUDE.md, Classes/GEMINI.md, Configuration/AGENTS.md, Configuration/CLAUDE.md, Configuration/GEMINI.md, Documentation/AGENTS.md, GEMINI.md, Resources/AGENTS.md, Resources/CLAUDE.md, Resources/GEMINI.md, Tests/AGENTS.md, Tests/CLAUDE.md, Tests/E2E/AGENTS.md, Tests/E2E/CLAUDE.md, Tests/E2E/GEMINI.md, Tests/GEMINI.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files.ddev/AGENTS.md, .ddev/CLAUDE.md, .ddev/GEMINI.md, .github/workflows/AGENTS.md, .github/workflows/CLAUDE.md, .github/workflows/GEMINI.md, AGENTS.md, CLAUDE.md, Classes/AGENTS.md, Classes/CLAUDE.md, Classes/GEMINI.md, Configuration/AGENTS.md, Configuration/CLAUDE.md, Configuration/GEMINI.md, Documentation/AGENTS.md, GEMINI.md, Resources/AGENTS.md, Resources/CLAUDE.md, Resources/GEMINI.md, Tests/AGENTS.md, Tests/CLAUDE.md, Tests/E2E/AGENTS.md, Tests/E2E/CLAUDE.md, Tests/E2E/GEMINI.md, Tests/GEMINI.md
agent_instruction_max_bytes11,308
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
54.7/55Manageable file sizes2/330 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes90,661
source_files_sampled330
oversized_source_files2

Key facts

2GitHub stars
4contributors
918commits, last 12 months
0days since last push
20releases
1bus factor
2open issues
npm, Packagistpackage ecosystems

More detail

OpenSSF Scorecard 8.3 / 10
8.3aggregate

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-07-16 00:56 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
7CII-Best-Practicesbadge detected: Silver
10Code-Reviewall changesets reviewed
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagisttypo3/cms-core^13.4 || ^14.3composer.json
Packagisttypo3/cms-backend^13.4 || ^14.3composer.json
Packagisttypo3/cms-install^13.4 || ^14.3composer.json
Packagistpsr/http-client^1.0composer.json
Packagistpsr/http-factory^1.0composer.json
All dependencies 14

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

RegistryPackageVersionRelation
Packagistpsr/http-clientdirect
Packagistpsr/http-factorydirect
Packagisttypo3/cms-backenddirect
Packagisttypo3/cms-coredirect
Packagisttypo3/cms-installdirect
npm@axe-core/playwright^4.10.0indirect
npm@playwright/test^1.57.0indirect
Packagistext-jsonindirect
Packagistext-sodiumindirect
Packagistmikey179/vfsstreamindirect
Packagistnetresearch/typo3-ci-workflowsindirect
Packagistphpindirect
Packagistroave/security-advisoriesindirect
Packagisttypo3/cms-schedulerindirect
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.11.0 — full methodology · metrics wiki.

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