Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-08 23:39 UTC

netresearch / t3x-nr-vault

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

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

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

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

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

Ownership

Netresearch DTT GmbHOrganization · verified domain
43 followers286 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?

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 1,352 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,352
human_commit_share0.84
days_since_last_push0
active_weeks_last_year35

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 33 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~5.1 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count33
latest_release_tagv0.16.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases5.1

Community & Adoption

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

50Moderate · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars3
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges10
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesapi.securityscorecards.dev, codecov.io, github.com, shields.io, www.bestpractices.dev
has_pull_request_templateyes
How it's scored
59.7/80Monthly downloads — 29,880 downloads/month across packagist
3.2/20Registry dependents — 2 packages depend on it
Inputs used
packagesnetresearch/nr-vault
dependents2
ecosystemspackagist
total_downloads90,076
monthly_downloads29,880
unverified_packages_excluded—

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
37.2/42Issue resolution — 88% of issues closed
28.8/30PR acceptance — 302/315 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs302
open_issues3
closed_issues23
prs_merged_7d2
prs_decided_7d2
prs_merged_30d25
prs_decided_30d25
issue_closed_ratio0.885
closed_unmerged_prs13
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
20/20Verified domain
11.8/25Owner reach — 43 followers of netresearch
25/25Track record — 286 public repos, account ~16 yr old
Inputs used
followers43
owner_typeOrganization
is_verifiedyes
owner_loginnetresearch
public_repos286
account_age_days6,146

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 4 days ago
20/20Version history — 33 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnetresearch/nr-vault
ecosystemspackagist
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 12 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-Tests — 14 out of 14 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/10Topics — 1 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?

85Excellent · 16% of overall

Security posture

85Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
1.8/2.5CII-Best-Practices — badge detected: Silver
7.5/7.5Code-Review — all changesets reviewed
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
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 21 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate8.5
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.

76Good · 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, Documentation/CLAUDE.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)
40/40Legible commit history — 82 of 84 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.976
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, Documentation/CLAUDE.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,553
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
53.9/55Manageable file sizes — 11/553 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes171,043
source_files_sampled553
oversized_source_files11

Key facts

3GitHub stars
1contributors
1,352commits, last 12 months
0days since last push
33releases
1bus factor
3open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 8.5 / 10
8.5aggregate

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-08 23:39 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 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 21 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 6
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
Packagistguzzlehttp/guzzle^7.10composer.json
Packagistpsr/http-client^1.0composer.json
Packagistpsr/http-factory^1.0composer.json
All dependencies 16

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzle—direct
Packagistpsr/http-client—direct
Packagistpsr/http-factory—direct
Packagisttypo3/cms-backend—direct
Packagisttypo3/cms-core—direct
Packagisttypo3/cms-install—direct
npm@axe-core/playwright^4.10.0indirect
npm@playwright/test^1.57.0indirect
Packagistext-json—indirect
Packagistext-sodium—indirect
Packagistmikey179/vfsstream—indirect
Packagistnetresearch/typo3-ci-workflows—indirect
Packagistphp—indirect
Packagistroave/security-advisories—indirect
Packagisttypo3/cms-dashboard—indirect
Packagisttypo3/cms-scheduler—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — Packagist.