Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 20:56 UTC

JBZoo / Toolbox-Dev

Package includes tools to debug and gathering stats for all JBZoo projects.

PHP · MakefileMIT★ 1 star⑂ 0 forkssince May 2020View on GitHub ↗

JBZoo/Toolbox-Dev holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (61/100) and lowest on Security (28/100). It was last updated 24 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 49 is calibrated to 48 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

JBZoo ToolboxOrganization
10 followers33 public repossince Jul 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistjbzoo/toolbox-dev8.0.09,8284124 days agodebugdeveloperdevtoolboxjbzoodevkitdev-kit

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 24 days ago
1.4/36Commit cadence2/52 weeks with commits
8.1/18Commit volume7 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year7
human_commit_share1
days_since_last_push24
active_weeks_last_year2
How it's scored
27/27Ships releases41 releases published
36/36Release recencylatest release 24 days ago
12.6/27Release cadencea release every ~167.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count41
latest_release_tag8.0.0
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases167.4
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?

33At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, poser.pugx.org, shields.io
has_pull_request_templateno
How it's scored
53.2/80Monthly downloads9,828 downloads/month across packagist
8.9/20Registry dependents21 packages depend on it
Inputs used
packagesjbzoo/toolbox-dev
dependents21
ecosystemspackagist
total_downloads1,053,186
monthly_downloads9,828
unverified_packages_excluded

Sustainability & Governance

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

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
28.5/30PR acceptance19/20 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs19
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
7.5/25Owner reach10 followers of JBZoo
23.2/25Track record33 public repos, account ~11 yr old
Inputs used
followers10
owner_typeOrganization
is_verified
owner_loginJBZoo
public_repos33
account_age_days4,049
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 24 days ago
20/20Version history41 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjbzoo/toolbox-dev
ecosystemspackagist
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests3 out of 18 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
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
10/10Topics7 topics
0/10Wiki
Inputs used
topicsjbzoo, debug, php, dev-tools, codestyle, standards, linters
has_wikino
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?

28At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests3 out of 18 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/22 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
0/5Pinned-Dependenciesno data
1/5SASTSAST tool is not run on all commits -- score normalized to 2
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.8
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier28
security_posture_before_jurisdiction37
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

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.

51Moderate · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
12/40Legible commit history21 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.226
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes3,133
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 93
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
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 codePHP without a type-check config
55/55Manageable file sizes0/6 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes1,464
source_files_sampled6
oversized_source_files0

Key facts

1GitHub stars
1contributors
7commits, last 12 months
24days since last push
41releases
1bus factor
0open issues
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 3.8 / 10
3.8aggregate

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-08-13 20:56 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
1CI-Tests3 out of 18 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/22 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
2SASTSAST tool is not run on all commits -- score normalized to 2
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagistjbzoo/phpunit^8.0composer.json
Packagistjbzoo/codestyle^8.0composer.json
Packagistjbzoo/markdown^8.0composer.json
Packagistsymfony/var-dumper>=7.3.4composer.json
Packagistfakerphp/faker>=1.24.1composer.json
All dependencies 7

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

RegistryPackageVersionRelation
Packagistfakerphp/fakerdirect
Packagistjbzoo/codestyledirect
Packagistjbzoo/markdowndirect
Packagistjbzoo/phpunitdirect
Packagistsymfony/var-dumperdirect
Packagistphpindirect
Packagistphp-coveralls/php-coverallsindirect
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.31.0 — full methodology · metrics wiki.

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