Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 04:58 UTC

jonom / silverstripe-betternavigator

Front-end utility menu for SilverStripe websites featuring administration and development tools

SCSS · PHP · SchemeNo license detected★ 59 stars⑂ 29 forkssince Aug 2014View on GitHub ↗

jonom/silverstripe-betternavigator holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (64/100) and lowest on AI Readiness (17/100). It was last updated 91 days ago. A single contributor accounts for most of its recent work.

31
overall / 100
At Risk

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.

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

Ownership

Jono MenzPersonal account
102 followers57 public repossince Sep 2011Independent Developer

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
Packagistjonom/silverstripe-betternavigator7.1.05,5272691 days agosilverstripenavigatorsilverstripenavigatorbetternavigator

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 recencylast push 91 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share
days_since_last_push91
active_weeks_last_year1
How it's scored
27/27Ships releases26 releases published
27/36Release recencylatest release 91 days ago
12.6/27Release cadencea release every ~216.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count26
latest_release_tag7.1.0
releases_from_tagsno
days_since_latest_release91
mean_days_between_releases216.6
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
28.6/60Stars59 stars
12.1/25Forks29 forks
3.9/15Watchers6 watchers
Inputs used
forks29
stars59
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
49.9/80Monthly downloads5,527 downloads/month across packagist
7.2/20Registry dependents11 packages depend on it
Inputs used
packagesjonom/silverstripe-betternavigator
dependents11
ecosystemspackagist
total_downloads438,093
monthly_downloads5,527
unverified_packages_excluded

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
9/54Bus factor1 contributor(s) cover half of all commits
8.1/22.5Commit distributiontop contributor authored 64% of commits
13.5/13.5Contributor breadth20 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.639
How it's scored
34.8/42Issue resolution83% of issues closed
21.1/30PR acceptance31/44 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 17/29 approved changesets -- score normalized to 5
Inputs used
merged_prs31
open_issues5
closed_issues24
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.828
closed_unmerged_prs13
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.5/25Owner reach102 followers of jonom
24.8/25Track record57 public repos, account ~14 yr old
Inputs used
followers102
owner_typeUser
is_verified
owner_loginjonom
public_repos57
account_age_days5,408
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 91 days ago
20/20Version history26 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjonom/silverstripe-betternavigator
ecosystemspackagist
any_deprecatedno
min_days_since_publish91

Engineering Quality

Are baseline engineering and documentation practices in place?

24At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

17Critical · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 17/29 approved changesets -- score normalized to 5
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, 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.

17Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
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
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeSCSS without a type-check config
55/55Manageable file sizes0/3 source files over 60KB
Inputs used
primary_languageSCSS
largest_source_bytes8,543
source_files_sampled3
oversized_source_files0

Key facts

59GitHub stars
20contributors
1commits, last 12 months
91days since last push
26releases
1bus factor
5open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Could not fetch npm package 'silverstripe-betternavigator' from its registry

More detail

OpenSSF Scorecard 1.7 / 10
1.7aggregate

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-17 04:57 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 17/29 approved changesets -- score normalized to 5
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistsilverstripe/framework^6composer.json
All dependencies 132

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

RegistryPackageVersionRelation
Packagistsilverstripe/frameworkdirect
npm@colors/colors1.5.0indirect
npm@dabh/diagnostics2.0.3indirect
npm@resvg/resvg-js2.4.1indirect
npm@resvg/resvg-js-android-arm-eabi2.4.1indirect
npm@resvg/resvg-js-android-arm642.4.1indirect
npm@resvg/resvg-js-darwin-arm642.4.1indirect
npm@resvg/resvg-js-darwin-x642.4.1indirect
npm@resvg/resvg-js-linux-arm-gnueabihf2.4.1indirect
npm@resvg/resvg-js-linux-arm64-gnu2.4.1indirect
npm@resvg/resvg-js-linux-arm64-musl2.4.1indirect
npm@resvg/resvg-js-linux-x64-gnu2.4.1indirect
npm@resvg/resvg-js-linux-x64-musl2.4.1indirect
npm@resvg/resvg-js-win32-arm64-msvc2.4.1indirect
npm@resvg/resvg-js-win32-ia32-msvc2.4.1indirect
npm@resvg/resvg-js-win32-x64-msvc2.4.1indirect
npm@trysound/sax0.2.0indirect
npm@types/triple-beam1.3.2indirect
npm@xmldom/xmldom0.8.10indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmargparse2.0.1indirect
npmasync3.2.4indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.2.0indirect
npmboolbase1.0.0indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.2indirect
npmchokidar3.5.3indirect
npmcliui8.0.1indirect
npmclone2.1.2indirect
npmclone-buffer1.0.0indirect
npmclone-stats1.0.0indirect
npmcloneable-readable1.1.3indirect
npmcolor3.2.1indirect
npmcolor-convert1.9.3indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.3indirect
npmcolor-name1.1.4indirect
npmcolor-string1.9.1indirect
npmcolorspace1.1.4indirect
npmcommander7.2.0indirect
npmconcat-map0.0.1indirect
npmcore-util-is1.0.3indirect
npmcss-select4.3.0indirect
npmcss-selector-parser1.4.1indirect
npmcss-tree1.1.3indirect
npmcss-what6.1.0indirect
npmcsso4.2.0indirect
npmcssom0.5.0indirect
npmdom-serializer1.4.1indirect
npmdomelementtype2.3.0indirect
npmdomhandler4.3.1indirect
npmdomutils2.8.0indirect
npmemoji-regex8.0.0indirect
npmenabled2.0.0indirect
npmentities2.2.0indirect
npmescalade3.1.1indirect
npmfecha4.2.3indirect
npmfill-range7.0.1indirect
npmfn.name1.1.0indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.2indirect
npmget-caller-file2.0.5indirect
npmglob7.2.3indirect
npmglob-parent5.1.2indirect
npmimmutable4.3.1indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-arrayish0.3.2indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-stream2.0.1indirect
npmisarray1.0.0indirect
npmjs-yaml4.1.0indirect
npmkuler2.0.0indirect
npmlodash.escape4.0.1indirect
npmlodash.merge4.6.2indirect
npmlodash.trim4.5.1indirect
npmlodash.trimstart4.5.1indirect
npmlogform2.5.1indirect
npmmdn-data2.0.14indirect
npmminimatch3.1.2indirect
npmms2.1.3indirect
npmmustache4.2.0indirect
npmnormalize-path3.0.0indirect
npmnth-check2.1.1indirect
npmonce1.4.0indirect
npmone-time1.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpicocolors1.0.0indirect
npmpicomatch2.3.1indirect
npmprettysize2.0.0indirect
npmprocess-nextick-args2.0.1indirect
npmreadable-stream2.3.8indirect
npmreadable-stream3.6.2indirect
npmreaddirp3.6.0indirect
npmremove-trailing-separator1.1.0indirect
npmreplace-ext1.0.1indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.1.2indirect
npmsafe-buffer5.2.1indirect
npmsafe-stable-stringify2.4.3indirect
npmsass1.64.1indirect
npmsimple-swizzle0.2.2indirect
npmsource-map0.6.1indirect
npmsource-map-js1.0.2indirect
npmstable0.1.8indirect
npmstack-trace0.0.10indirect
npmstring-width4.2.3indirect
npmstring_decoder1.1.1indirect
npmstring_decoder1.3.0indirect
npmstrip-ansi6.0.1indirect
npmsvg-sprite2.0.2indirect
npmsvgo2.8.0indirect
npmtext-hex1.0.0indirect
npmto-regex-range5.0.1indirect
npmtriple-beam1.4.1indirect
npmutil-deprecate1.0.2indirect
npmvinyl2.2.1indirect
npmwinston3.10.0indirect
npmwinston-transport4.5.0indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmxpath0.0.32indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
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.