Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-06 12:52 UTC

duncan3dc / blade

Use Blade templates without the full Laravel framework

PHPApache-2.0★ 148 stars⑂ 36 forkssince Sep 2014View on GitHub ↗

duncan3dc/blade holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (70/100) and lowest on AI Readiness (34/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

Craig DuncanPersonal account
117 followers84 public repossince Jan 2011Estrato Cloud

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
Packagistduncan3dc/blade4.17.06,7853635 days agotemplatingtemplatelaravelviews

Metrics by category

Vitality

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

61Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0.7/36Commit cadence1/52 weeks with commits
9/18Commit volume9 commits in the last year
7/10OpenSSF Scorecard: Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year9
human_commit_share0.99
days_since_last_push0
active_weeks_last_year1
How it's scored
16.2/27Ships releases36 version tags (no GitHub releases)
36/36Release recencylatest release 35 days ago
12.6/27Release cadencea release every ~272.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count36
latest_release_tag4.17.0
releases_from_tagsyes
days_since_latest_release35
mean_days_between_releases272.7
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?

53Moderate · 17% of overall
How it's scored
35.2/60Stars148 stars
12.9/25Forks36 forks
3.3/15Watchers5 watchers
Inputs used
forks36
stars148
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, poser.pugx.org
has_pull_request_templateno
How it's scored
51.1/80Monthly downloads6,785 downloads/month across packagist
10.4/20Registry dependents35 packages depend on it
Inputs used
packagesduncan3dc/blade
dependents35
ecosystemspackagist
total_downloads514,619
monthly_downloads6,785
unverified_packages_excluded

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.7/22.5Commit distributiontop contributor authored 97% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.967
How it's scored
38.5/42Issue resolution92% of issues closed
10.7/30PR acceptance5/14 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues2
closed_issues22
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.917
closed_unmerged_prs9
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.9/25Owner reach117 followers of duncan3dc
25/25Track record84 public repos, account ~15 yr old
Inputs used
followers117
owner_typeUser
is_verified
owner_loginduncan3dc
public_repos84
account_age_days5,693
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 35 days ago
20/20Version history36 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesduncan3dc/blade
ecosystemspackagist
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configphpcs.xml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsphp, blade-template, laravel-framework, templating
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?

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 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
5.2/7.5Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, 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.

34At Risk · 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 history0 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpcs.xml
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/39 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes10,620
source_files_sampled39
oversized_source_files0

Key facts

148GitHub stars
7contributors
9commits, last 12 months
0days since last push
36releases
1bus factor
2open 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 ★ / 36 ⇿
0Stars
36Forks
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.

01325383522015-052019-092024-02
Major 2Minor 16Patch 4

Each point covers 8 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-06 12:52 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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 5
RegistryPackageVersion constraintManifest
Packagistilluminate/contracts^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/events^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/filesystem^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/support^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/view^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
All dependencies 15

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

RegistryPackageVersionRelation
Packagistilluminate/contractsdirect
Packagistilluminate/eventsdirect
Packagistilluminate/filesystemdirect
Packagistilluminate/supportdirect
Packagistilluminate/viewdirect
Packagistduncan3dc/object-intruderindirect
Packagistmaglnet/composer-require-checkerindirect
Packagistmockery/mockeryindirect
Packagistnikic/php-parserindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-mockeryindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpunit/phpunitindirect
Packagistsquizlabs/php_codesnifferindirect
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.