Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 14:01 UTC

jonom / silverstripe-betternavigator

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

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

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

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

34
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 39 is calibrated to 34 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,49626145 days agosilverstripenavigatorsilverstripenavigatorbetternavigator

Metrics by category

Vitality

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

39Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 145 days ago
0.7/36Commit cadence — 1/52 weeks with commits
2.7/18Commit volume — 1 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year1
human_commit_share1
days_since_last_push145
active_weeks_last_year1
How it's scored
27/27Ships releases — 26 releases published
27/36Release recency — latest release 145 days ago
12.6/27Release cadence — a release every ~216.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tag7.1.0
releases_from_tagsno
days_since_latest_release145
mean_days_between_releases216.6

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/60Stars — 59 stars
11.9/25Forks — 28 forks
3.9/15Watchers — 6 watchers
Inputs used
forks28
stars59
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
49.9/80Monthly downloads — 5,496 downloads/month across packagist
7.2/20Registry dependents — 11 packages depend on it
Inputs used
packagesjonom/silverstripe-betternavigator
dependents11
ecosystemspackagist
total_downloads448,609
monthly_downloads5,496
unverified_packages_excluded—

Sustainability & Governance

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

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.1/22.5Commit distribution — top contributor authored 64% of commits
13.5/13.5Contributor breadth — 20 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.639
How it's scored
34.8/42Issue resolution — 83% of issues closed
21.1/30PR acceptance — 31/44 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs31
open_issues5
closed_issues24
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.828
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.5/25Owner reach — 102 followers of jonom
24.8/25Track record — 57 public repos, account ~14 yr old
Inputs used
followers102
owner_typeUser
is_verified—
owner_loginjonom
public_repos57
account_age_days5,462
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 packagist
35/35Publish recency — latest publish 145 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjonom/silverstripe-betternavigator
ecosystemspackagist
any_deprecatedno
min_days_since_publish145

Engineering Quality

Are baseline engineering and documentation practices in place?

25At 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-Tests — no data
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?

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestscomposer.json, package.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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
advisories39
affected_packages9
assessed_packages131
unassessed_packages1
affected_by_severitycritical 1, high 7, moderate 1
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 131 resolved dependencies against OSV. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

22At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.3/40Legible commit history — 30 of 75 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.4
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 75
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no 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_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — SCSS without a type-check config
55/55Manageable file sizes — 0/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
145days since last push
26releases
1bus factor
5open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'silverstripe-betternavigator' from its registry
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/jonom/silverstripe-betternavigator: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-09T14:01:36Z. Please include `C60E:277E59:12AA436:120F157:6AA166BD` when reporting this issue.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 28 ⇿
0Stars
28Forks
22Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0510152025302712014-082019-012023-06
Major 5Minor 6Patch 10

Each point covers 9 days.

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/framework—direct
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
Dependency advisories 9

This repository publishes no package the index resolves, so its own dependency graph was assessed — 131 packages, which also include development and test pins that never ship: 9 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
immutable4.3.1indirectcritical35.1.8
@xmldom/xmldom0.8.10indirecthigh150.9.12
brace-expansion1.1.11indirecthigh55.0.9
braces3.0.2indirecthigh13.0.3
js-yaml4.1.0indirecthigh54.3.2
minimatch3.1.2indirecthigh310.2.3
picomatch2.3.1indirecthigh24.0.4
svgo2.8.0indirecthigh44.1.0
lodash.trim4.5.1indirectmoderate14.17.21

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.