Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 20:56 UTC

simplesamlphp / saml2

SimpleSAMLphp low-level SAML2 PHP library

PHPLGPL-2.1★ 305 stars⑂ 137 forkssince Nov 2013View on GitHub ↗

simplesamlphp/saml2 holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on AI Readiness (31/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

SimpleSAMLphpOrganization · verified domain
30 followers91 public repossince Oct 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistsimplesamlphp/saml2v7.0.0-rc1264,27918240 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
21.5/36Commit cadence31/52 weeks with commits
18/18Commit volume138 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year138
human_commit_share0.94
days_since_last_push0
active_weeks_last_year31
How it's scored
27/27Ships releases56 releases published
36/36Release recencylatest release 39 days ago
12.6/27Release cadencea release every ~256.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count56
latest_release_tagv7.0.0-rc1
releases_from_tagsno
days_since_latest_release39
mean_days_between_releases256.2
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?

65Good · 17% of overall
How it's scored
40.3/60Stars305 stars
17.8/25Forks137 forks
8.4/15Watchers33 watchers
Inputs used
forks137
stars305
watchers33
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (LGPL-2.1)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com
has_pull_request_templateno
How it's scored
72.3/80Monthly downloads264,279 downloads/month across packagist
10.8/20Registry dependents40 packages depend on it
Inputs used
packagessimplesamlphp/saml2
dependents40
ecosystemspackagist
total_downloads18,515,576
monthly_downloads264,279
unverified_packages_excluded

Sustainability & Governance

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

79Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
13.9/22.5Commit distributiontop contributor authored 38% of commits
13.5/13.5Contributor breadth47 contributors
10/10OpenSSF Scorecard: Contributorsproject has 20 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled47
top_contributor_share0.384
How it's scored
38.3/42Issue resolution91% of issues closed
25.9/30PR acceptance254/294 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/19 approved changesets -- score normalized to 1
Inputs used
merged_prs254
open_issues11
closed_issues114
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.912
closed_unmerged_prs40
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
10.7/25Owner reach30 followers of simplesamlphp
25/25Track record91 public repos, account ~12 yr old
Inputs used
followers30
owner_typeOrganization
is_verifiedyes
owner_loginsimplesamlphp
public_repos91
account_age_days4,684

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 40 days ago
20/20Version history182 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessimplesamlphp/saml2
ecosystemspackagist
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configphpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
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://www.simplesamlphp.org
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicssaml2, saml, php, simplesamlphp, library
has_wikiyes
homepagehttps://www.simplesamlphp.org
docs_sitehttps://www.simplesamlphp.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

50Moderate · 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
0/2.5CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 2/19 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 20 contributing companies or organizations
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
7.5/7.5Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
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_aggregate4.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.

31At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
5.7/40Legible commit history10 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.106
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpcs.xml, phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance6 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_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.06
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/542 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes55,107
source_files_sampled542
oversized_source_files0

Key facts

305GitHub stars
47contributors
138commits, last 12 months
0days since last push
56releases
2bus factor
11open 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 ★ / 137 ⇿
0Stars
137Forks
56Releases

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.

025507510012515013442014-012020-042026-08
Major 5Minor 4Patch 40

Each point covers 12 days.

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

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 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/19 approved changesets -- score normalized to 1
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
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 8
RegistryPackageVersion constraintManifest
Packagistnyholm/psr7~1.8composer.json
Packagistpsr/clock~1.0composer.json
Packagistpsr/http-message~2.0composer.json
Packagistpsr/log~3.0composer.json
Packagistsimplesamlphp/assert~3.0composer.json
Packagistsimplesamlphp/xml-common~3.0composer.json
Packagistsimplesamlphp/xml-security^3.0composer.json
Packagistsimplesamlphp/xml-soap^3.0composer.json
All dependencies 21

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

RegistryPackageVersionRelation
Packagistnyholm/psr7direct
Packagistpsr/clockdirect
Packagistpsr/http-messagedirect
Packagistpsr/logdirect
Packagistsimplesamlphp/assertdirect
Packagistsimplesamlphp/xml-commondirect
Packagistsimplesamlphp/xml-securitydirect
Packagistsimplesamlphp/xml-soapdirect
Packagistbeste/clockindirect
Packagistext-dateindirect
Packagistext-domindirect
Packagistext-filterindirect
Packagistext-intlindirect
Packagistext-opensslindirect
Packagistext-pcreindirect
Packagistext-zlibindirect
Packagisticanhazstring/composer-unusedindirect
Packagistmockery/mockeryindirect
Packagistphpindirect
Packagistsimplesamlphp/simplesamlphpindirect
Packagistsimplesamlphp/simplesamlphp-test-frameworkindirect
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.