Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-08 01:46 UTC

contenir / contenir-db-model

PHPBSD-3-Clause★ 0 stars⑂ 0 forkssince Apr 2023View on GitHub ↗

contenir/contenir-db-model holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Vitality (75/100) and lowest on Community & Adoption (31/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

ContenirOrganization
1 follower37 public repossince Dec 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistcontenir/contenir-db-modelv2.0.0-rc42,224260 days agoormrepositorydata-mapperphp-dbcontenir

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
1.4/36Commit cadence — 2/52 weeks with commits
16.3/18Commit volume — 65 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year65
human_commit_share0.901
days_since_last_push0
active_weeks_last_year2
How it's scored
27/27Ships releases — 24 releases published
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~81 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count24
latest_release_tagv2.0.0-rc4
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases81
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?

31At Risk · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com
has_pull_request_templateno
How it's scored
44.6/80Monthly downloads — 2,224 downloads/month across packagist
6.4/20Registry dependents — 8 packages depend on it
Inputs used
packagescontenir/contenir-db-model
dependents8
ecosystemspackagist
total_downloads2,924
monthly_downloads2,224
unverified_packages_excluded—

Sustainability & Governance

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

59Moderate · 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
42/42Issue resolution — 100% of issues closed
30/30PR acceptance — 20/20 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs20
open_issues0
closed_issues10
prs_merged_7d10
prs_decided_7d10
prs_merged_30d10
prs_decided_30d10
issue_closed_ratio1
closed_unmerged_prs0
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
2.2/25Owner reach — 1 followers of contenir
21.2/25Track record — 37 public repos, account ~4 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_logincontenir
public_repos37
account_age_days1,768

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 0 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescontenir/contenir-db-model
ecosystemspackagist
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://contenir.com.au
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://contenir.com.au
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages69
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 69 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt present
29.3/40Legible commit history — 45 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.549
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 91
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
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
55/55Manageable file sizes — 0/217 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes15,980
source_files_sampled217
oversized_source_files0

Key facts

0GitHub stars
1contributors
65commits, last 12 months
0days since last push
24releases
1bus factor
0open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 4.3 / 10
4.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-10-08 01:46 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistpsr/container^1.1 || ^2.0composer.json
Packagistpsr/simple-cache^1.0 || ^2.0 || ^3.0composer.json
All dependencies 69

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

RegistryPackageVersionRelation
Packagistpsr/container2.0.2direct
Packagistpsr/simple-cache3.0.0direct
Packagistbrick/varexporter0.6.0indirect
Packagistcolinodell/json53.0.0indirect
Packagistcomposer/pcre3.4.0indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistcontenir/contenir-qa-tools 0.1-dev.0indirect
Packagistfidry/cpu-core-counter1.4.1indirect
Packagistinfection/abstract-testframework-adapter0.5.1indirect
Packagistinfection/extension-installer0.1.2indirect
Packagistinfection/include-interceptor1.0.0indirect
Packagistinfection/infection0.34.2indirect
Packagistinfection/mutator0.4.1indirect
Packagistjustinrainbow/json-schema6.13.1indirect
Packagistlaminas/laminas-servicemanager4.5.1indirect
Packagistlaminas/laminas-stdlib3.21.0indirect
Packagistmarc-mabe/php-enum4.7.2indirect
Packagistmyclabs/deep-copy1.14.0indirect
Packagistnikic/php-parser5.9.0indirect
Packagistondram/ci-detector4.2.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphp-db/phpdb 0.6-dev.0indirect
Packagistphp-db/phpdb-mysql0.4.0indirect
Packagistphp-db/phpdb-pgsql 0.1-dev.0indirect
Packagistphp-db/phpdb-sqlite0.2.0indirect
Packagistphpunit/php-code-coverage11.0.12indirect
Packagistphpunit/php-file-iterator5.1.1indirect
Packagistphpunit/php-invoker5.0.1indirect
Packagistphpunit/php-text-template4.0.1indirect
Packagistphpunit/php-timer7.0.1indirect
Packagistphpunit/phpunit11.5.56indirect
Packagistpsr/clock1.0.0indirect
Packagistpsr/log3.0.2indirect
Packagistsanmai/di-container0.1.23indirect
Packagistsanmai/duoclock0.1.3indirect
Packagistsanmai/later0.1.8indirect
Packagistsanmai/pipeline7.12indirect
Packagistsebastian/cli-parser3.0.2indirect
Packagistsebastian/code-unit3.0.3indirect
Packagistsebastian/code-unit-reverse-lookup4.0.1indirect
Packagistsebastian/comparator6.3.3indirect
Packagistsebastian/complexity4.0.1indirect
Packagistsebastian/diff6.0.2indirect
Packagistsebastian/environment7.2.1indirect
Packagistsebastian/exporter6.3.2indirect
Packagistsebastian/global-state7.0.2indirect
Packagistsebastian/lines-of-code3.0.1indirect
Packagistsebastian/object-enumerator6.0.1indirect
Packagistsebastian/object-reflector4.0.1indirect
Packagistsebastian/recursion-context6.0.3indirect
Packagistsebastian/type5.1.3indirect
Packagistsebastian/version5.0.2indirect
Packagiststaabm/side-effects-detector1.0.5indirect
Packagistsymfony/console7.4.20indirect
Packagistsymfony/deprecation-contracts3.7.1indirect
Packagistsymfony/filesystem7.4.18indirect
Packagistsymfony/finder7.4.20indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.43.0indirect
Packagistsymfony/polyfill-intl-normalizer1.43.0indirect
Packagistsymfony/polyfill-mbstring1.43.0indirect
Packagistsymfony/polyfill-php851.43.0indirect
Packagistsymfony/process7.4.19indirect
Packagistsymfony/service-contracts3.7.3indirect
Packagistsymfony/string7.4.19indirect
Packagistthecodingmachine/safe3.4.0indirect
Packagisttheseer/tokenizer1.3.1indirect
Packagistwebmozart/assert2.4.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 69 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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