Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 22:01 UTC

ellaisys / aws-cognito

AWS Cognito package (with MFA, SRP and Passkeys Feature) for PHP/Laravel

PHP · BladeCustom license★ 123 stars⑂ 57 forkssince Aug 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ellaisys/aws-cognito holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (94/100) and lowest on AI Readiness (37/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

EllaiSysOrganization
2 followers149 public repossince Jun 2016

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

Package ecosystems

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
25.6/36Commit cadence — 37/52 weeks with commits
18/18Commit volume — 827 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year827
human_commit_share0.94
days_since_last_push0
active_weeks_last_year37

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 53 releases published
36/36Release recency — latest release 21 days ago
27/27Release cadence — a release every ~22.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count53
latest_release_tagv2.0.9
releases_from_tagsno
days_since_latest_release21
mean_days_between_releases22.3
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?

62Moderate · 17% of overall
How it's scored
33.8/60Stars — 123 stars
14.6/25Forks — 57 forks
1.7/15Watchers — 3 watchers
Inputs used
forks57
stars123
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges22
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io, sonarcloud.io
has_pull_request_templateno
How it's scored
55.8/80Monthly downloads — 15,376 downloads/month across packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagesellaisys/aws-cognito
dependents1
ecosystemspackagist
total_downloads311,249
monthly_downloads15,376
unverified_packages_excluded—

Sustainability & Governance

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

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.1/22.5Commit distribution — top contributor authored 73% of commits
13.5/13.5Contributor breadth — 15 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.731
How it's scored
39.6/42Issue resolution — 94% of issues closed
24.8/30PR acceptance — 52/63 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/14 approved changesets -- score normalized to 1
Inputs used
merged_prs52
open_issues5
closed_issues81
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.942
closed_unmerged_prs11
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of ellaisys
25/25Track record — 149 public repos, account ~10 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginellaisys
public_repos149
account_age_days3,775

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 21 days ago
20/20Version history — 53 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesellaisys/aws-cognito
ecosystemspackagist
any_deprecatedno
min_days_since_publish21

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://ellaisys.github.io/aws-cognito/
10/10Repository description
10/10Topics — 19 topics
10/10Wiki
Inputs used
topicsaws-cognito, laravel-cognito, aws-sdk, cognito-pool, user-pool, php, laravel, api-authentication, authentication-middleware, authentication, jwt, laravel-package, google-authenticator, mfa, cognito, fido2, passkeys, passwordless, device-authentication
has_wikiyes
homepagehttps://ellaisys.github.io/aws-cognito/
docs_sitehttps://ellaisys.github.io/aws-cognito/
has_readmeyes
has_docs_diryes
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-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/14 approved changesets -- score normalized to 1
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
5/5SAST — SAST tool is run on all commits
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.1
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.

37Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 90 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.957
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.02
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 code — PHP without a type-check config
54.4/55Manageable file sizes — 2/192 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes82,707
source_files_sampled192
oversized_source_files2

Key facts

123GitHub stars
15contributors
827commits, last 12 months
0days since last push
53releases
1bus factor
5open 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 ★ / 57 ⇿
0Stars
57Forks
38Releases

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.

01020304050605622021-062024-012026-09
Major 2Minor 4Patch 32

Each point covers 5 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-10-21 22:00 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/14 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
10SASTSAST tool is run on all commits
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
Packagistilluminate/console^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/contracts^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/database^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/http^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/log^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/notifications^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/pagination^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/routing^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/support^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/view^10.0|^11.0|^12.0|^13.0composer.json
Packagistguzzlehttp/guzzle^7.10composer.json
Packagistfirebase/php-jwt^7.0composer.json
Packagistaws/aws-sdk-php^3.380composer.json
Packagistsymfony/console^6.0|^7.0|^8.0composer.json
Packagistsymfony/http-kernel^5.4|^6.0|^7.0|^8.0composer.json
All dependencies 19

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

RegistryPackageVersionRelation
Packagistaws/aws-sdk-php—direct
Packagistfirebase/php-jwt—direct
Packagistguzzlehttp/guzzle—direct
Packagistilluminate/console—direct
Packagistilluminate/contracts—direct
Packagistilluminate/database—direct
Packagistilluminate/http—direct
Packagistilluminate/log—direct
Packagistilluminate/notifications—direct
Packagistilluminate/pagination—direct
Packagistilluminate/routing—direct
Packagistilluminate/support—direct
Packagistilluminate/view—direct
Packagistsymfony/console—direct
Packagistsymfony/http-kernel—direct
Packagistext-gmp—indirect
Packagistorchestra/testbench—indirect
Packagistphp—indirect
Packagistphpunit/phpunit—indirect
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 statistics — Packagist.