Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 06:27 UTC

anilkumarthakur60 / glide-laravel

Glide adapter for Laravel

PHPMIT★ 0 stars⑂ 0 forkssince Aug 2024forkView on GitHub ↗

anilkumarthakur60/glide-laravel holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (46/100) and lowest on Community & Adoption (21/100). It was last updated 142 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Er. Anil Kumar ThakurPersonal account
27 followers85 public repossince Jan 2016

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 publish
Packagistanil/glide-laravelv1.14,0872494 days ago

Metrics by category

Vitality

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

32At Risk · 21% of overall
How it's scored
9.9/36Push recencylast push 142 days ago
2.1/36Commit cadence3/52 weeks with commits
6.3/18Commit volume4 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year4
human_commit_share
days_since_last_push142
active_weeks_last_year3
How it's scored
27/27Ships releases2 releases published
7.2/36Release recencylatest release 494 days ago
12.6/27Release cadencea release every ~273.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagv1.1
releases_from_tagsno
days_since_latest_release494
mean_days_between_releases273.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?

21At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/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_readmeno
has_licenseno
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
48.2/80Monthly downloads4,087 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesanil/glide-laravel
dependents0
ecosystemspackagist
total_downloads44,203
monthly_downloads4,087
unverified_packages_excluded

Sustainability & Governance

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

36Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.9/22.5Commit distributiontop contributor authored 69% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.692
How it's scored
0/42Issue resolutionno issues or no data
2.8/30PR acceptance3/32 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs3
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs29
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.4/25Owner reach27 followers of anilkumarthakur60
25/25Track record85 public repos, account ~10 yr old
Inputs used
followers27
owner_typeUser
is_verified
owner_loginanilkumarthakur60
public_repos85
account_age_days3,902
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
14/35Publish recencylatest publish 494 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesanil/glide-laravel
ecosystemspackagist
any_deprecatedno
min_days_since_publish494

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests2 out of 3 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

25At Risk
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage sitehttp://glide.thephpleague.com
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttp://glide.thephpleague.com
docs_sitehttp://glide.thephpleague.com
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

39Weak · 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
1.5/2.5CI-Tests2 out of 3 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/8 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

26At 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
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
8/8Automated maintenance2 of the last 15 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_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0.133
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/2 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes1,327
source_files_sampled2
oversized_source_files0

Key facts

0GitHub stars
2contributors
4commits, last 12 months
142days since last push
2releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 3.9 / 10
3.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-09-13 06:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests2 out of 3 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/8 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Packagistleague/glide-symfony^2.0composer.json
Packagistleague/flysystem^3.0composer.json
Packagistintervention/image^2.4 || ^3.0composer.json
Packagistsymfony/http-foundation^5.0 || ^6.0 || ^7.0composer.json
All dependencies 6

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

RegistryPackageVersionRelation
Packagistintervention/imagedirect
Packagistleague/flysystemdirect
Packagistleague/glide-symfonydirect
Packagistsymfony/http-foundationdirect
Packagistmockery/mockeryindirect
Packagistphpunit/phpunitindirect
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.34.0 — full methodology · metrics wiki.

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