Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 14:08 UTC

brefphp / laravel-bridge

Laravel on AWS Lambda with Bref

PHPMIT★ 339 stars⑂ 71 forkssince Feb 2019View on GitHub ↗

brefphp/laravel-bridge holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (83/100) and lowest on AI Readiness (32/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

brefOrganization
108 followers30 public repossince Dec 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistbref/laravel-bridge3.0.6137,3885015 days agoawslambdaserverlessfaasbref

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
10.4/36Commit cadence15/52 weeks with commits
15.4/18Commit volume51 commits in the last year
10/10OpenSSF Scorecard: Maintained15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year51
human_commit_share
days_since_last_push0
active_weeks_last_year15

Release discipline

100Exceptional
How it's scored
27/27Ships releases50 releases published
36/36Release recencylatest release 15 days ago
27/27Release cadencea release every ~25.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count50
latest_release_tag3.0.6
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases25.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?

64Moderate · 17% of overall
How it's scored
41/60Stars339 stars
15.4/25Forks71 forks
6.4/15Watchers15 watchers
Inputs used
forks71
stars339
watchers15
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
68.5/80Monthly downloads137,388 downloads/month across packagist
6.9/20Registry dependents10 packages depend on it
Inputs used
packagesbref/laravel-bridge
dependents10
ecosystemspackagist
total_downloads4,634,214
monthly_downloads137,388
unverified_packages_excluded

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.3/22.5Commit distributiontop contributor authored 50% of commits
13.5/13.5Contributor breadth31 contributors
10/10OpenSSF Scorecard: Contributorsproject has 29 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled31
top_contributor_share0.499
How it's scored
28.3/42Issue resolution67% of issues closed
21.5/30PR acceptance73/102 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/9 approved changesets -- score normalized to 1
Inputs used
merged_prs73
open_issues28
closed_issues58
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.674
closed_unmerged_prs29
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
14.6/25Owner reach108 followers of brefphp
22.9/25Track record30 public repos, account ~7 yr old
Inputs used
followers108
owner_typeOrganization
is_verified
owner_loginbrefphp
public_repos30
account_age_days2,774
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 15 days ago
20/20Version history50 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbref/laravel-bridge
ecosystemspackagist
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
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://bref.sh/docs/frameworks/laravel.html
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsbref, serverless, lambda, aws-lambda, laravel, faas, sqs
has_wikino
homepagehttps://bref.sh/docs/frameworks/laravel.html
docs_sitehttps://bref.sh/docs/frameworks/laravel.html
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests9 out of 9 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.8/7.5Code-ReviewFound 1/9 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 29 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained15 commit(s) and 1 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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

32At 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 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
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
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 codePHP without a type-check config
55/55Manageable file sizes0/26 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes8,385
source_files_sampled26
oversized_source_files0

Key facts

339GitHub stars
31contributors
51commits, last 12 months
0days since last push
50releases
2bus factor
28open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 4.9 / 10
4.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-07-19 14:08 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
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/9 approved changesets -- score normalized to 1
10Contributorsproject has 29 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 1 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 12
RegistryPackageVersion constraintManifest
Packagistaws/aws-sdk-php^3.222composer.json
Packagistbref/bref^3.0.2composer.json
Packagistbref/laravel-health-check^1composer.json
Packagistbref/monolog-bridge^1.0composer.json
Packagistilluminate/container^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/contracts^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/http^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/queue^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/support^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistlaravel/octane^1.2 || ^2.0composer.json
Packagistlaravel/tinker^2.0 || ^3.0composer.json
Packagistriverline/multipart-parser^2.0composer.json
All dependencies 18

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

RegistryPackageVersionRelation
Packagistaws/aws-sdk-phpdirect
Packagistbref/brefdirect
Packagistbref/laravel-health-checkdirect
Packagistbref/monolog-bridgedirect
Packagistilluminate/containerdirect
Packagistilluminate/contractsdirect
Packagistilluminate/httpdirect
Packagistilluminate/queuedirect
Packagistilluminate/supportdirect
Packagistlaravel/octanedirect
Packagistlaravel/tinkerdirect
Packagistriverline/multipart-parserdirect
Packagistlarastan/larastanindirect
Packagistorchestra/testbenchindirect
Packagistphpindirect
Packagistphp-parallel-lint/php-parallel-lintindirect
Packagistphpunit/phpunitindirect
Packagistsquizlabs/php_codesnifferindirect
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.15.0 — full methodology · metrics wiki.

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