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

knuckleswtf / scribe

Generate API documentation for humans from your Laravel codebase.✍

PHP · CSSMIT★ 2,326 stars⑂ 356 forkssince May 2020View on GitHub ↗
KindLibraryNetwork servicehow this is determined

knuckleswtf/scribe holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on Security (59/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

KnucklesOrganization
29 followers9 public repossince Apr 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistknuckleswtf/scribe5.11.0849,81618566 days agodocumentationapilaravel

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.8/36Commit cadence17/52 weeks with commits
15.8/18Commit volume56 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year56
human_commit_share0.99
days_since_last_push0
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 66 days ago
27/27Release cadencea release every ~44.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag5.11.0
releases_from_tagsno
days_since_latest_release66
mean_days_between_releases44.8
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?

82Excellent · 17% of overall
How it's scored
54.6/60Stars2,326 stars
21.3/25Forks356 forks
6.4/15Watchers15 watchers
Inputs used
forks356
stars2,326
watchers15
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesposer.pugx.org, shields.io
has_pull_request_templateyes
How it's scored
79.1/80Monthly downloads849,816 downloads/month across packagist
11.2/20Registry dependents47 packages depend on it
Inputs used
packagesknuckleswtf/scribe
dependents47
ecosystemspackagist
total_downloads15,405,940
monthly_downloads849,816
unverified_packages_excluded

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.3/22.5Commit distributiontop contributor authored 72% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 39 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.719
How it's scored
36.7/42Issue resolution87% of issues closed
24/30PR acceptance266/332 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 17/28 approved changesets -- score normalized to 6
Inputs used
merged_prs266
open_issues93
closed_issues646
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.874
closed_unmerged_prs66
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
10.6/25Owner reach29 followers of knuckleswtf
19.3/25Track record9 public repos, account ~6 yr old
Inputs used
followers29
owner_typeOrganization
is_verified
owner_loginknuckleswtf
public_repos9
account_age_days2,318
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 66 days ago
20/20Version history185 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesknuckleswtf/scribe
ecosystemspackagist
any_deprecatedno
min_days_since_publish66

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests16 out of 19 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://scribe.knuckles.wtf/laravel/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://scribe.knuckles.wtf/laravel/
docs_sitehttps://scribe.knuckles.wtf/laravel/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 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
2/2.5CI-Tests16 out of 19 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 17/28 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 39 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.9
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.

68Good · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, AGENTS.md
0/15Machine-readable docs (llms.txt)
22.6/40Legible commit history42 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.424
agent_instruction_files.github/copilot-instructions.md, AGENTS.md
agent_instruction_max_bytes5,685
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile
6/10Demonstrated agent practice3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.03
toolchain_manifests
dependency_bot_commit_share0.01
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
54.8/55Manageable file sizes1/246 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes89,199
source_files_sampled246
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)tests/Fixtures/openapi.yaml
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filestests/Fixtures/openapi.yaml
interfaces_expected_ofnetwork-service

Key facts

2,326GitHub stars
99contributors
56commits, last 12 months
0days since last push
100releases
1bus factor
93open 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

Star and fork history 0 ★ / 356 ⇿
0Stars
356Forks
100Releases

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.

012525037535072020-052023-062026-08
Major 2Minor 75Patch 23

Each point covers 6 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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 22:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests16 out of 19 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 17/28 approved changesets -- score normalized to 6
10Contributorsproject has 39 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 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
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Packagistfakerphp/faker^1.23.1composer.json
Packagistlaravel/framework^9.21 || ^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistleague/flysystem^3.0composer.json
Packagistmpociot/reflection-docblock^1.0.1composer.json
Packagistnikic/php-parser^5.0composer.json
Packagistnunomaduro/collision^6.0 || ^7.0 || ^8.0composer.json
Packagistparsedown/parsedown^1.7composer.json
Packagistramsey/uuid^4.2.2composer.json
Packagistshalvah/upgrader^0.6.0composer.json
Packagistsymfony/var-exporter^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/yaml^6.0 || ^7.0 || ^8.0composer.json
All dependencies 26

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

RegistryPackageVersionRelation
Packagistfakerphp/fakerdirect
Packagistlaravel/frameworkdirect
Packagistleague/flysystemdirect
Packagistmpociot/reflection-docblockdirect
Packagistnikic/php-parserdirect
Packagistnunomaduro/collisiondirect
Packagistparsedown/parsedowndirect
Packagistramsey/uuiddirect
Packagistshalvah/upgraderdirect
Packagistsymfony/var-exporterdirect
Packagistsymfony/yamldirect
Packagistdms/phpunit-arraysubset-assertsindirect
Packagistext-fileinfoindirect
Packagistext-pdoindirect
Packagistlaravel/legacy-factoriesindirect
Packagistlaravel/pintindirect
Packagistleague/fractalindirect
Packagistnikic/fast-routeindirect
Packagistorchestra/testbenchindirect
Packagistpestphp/pestindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistspatie/rayindirect
Packagistsymfony/css-selectorindirect
Packagistsymfony/dom-crawlerindirect
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.