Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 15:48 UTC

AntCMS-org / AntLoader

A small, simple, and highly performant autoloader for PHP that's PSR-0 and PSR-4 compliant.

PHPApache-2.0★ 3 stars⑂ 1 forksince May 2023View on GitHub ↗

AntCMS-org/AntLoader holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (65/100) and lowest on Community & Adoption (30/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

AntCMSOrganization
1 follower8 public repossince Jan 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistantcms/antloader2.0.52,1909228 days ago

Metrics by category

Vitality

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

55Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.1/36Commit cadence3/52 weeks with commits
7/18Commit volume5 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year5
human_commit_share
days_since_last_push0
active_weeks_last_year3
How it's scored
27/27Ships releases9 releases published
16.2/36Release recencylatest release 228 days ago
19.8/27Release cadencea release every ~117.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count9
latest_release_tag2.0.5
releases_from_tagsno
days_since_latest_release228
mean_days_between_releases117.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?

30At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars3
watchers1
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
44.5/80Monthly downloads2,190 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesantcms/antloader
dependents0
ecosystemspackagist
total_downloads51,230
monthly_downloads2,190
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
3.2/22.5Commit distributiontop contributor authored 86% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.857
How it's scored
0/42Issue resolutionno issues or no data
28.3/30PR acceptance17/18 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/25 approved changesets -- score normalized to 0
Inputs used
merged_prs17
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
2.2/25Owner reach1 followers of AntCMS-org
14/25Track record8 public repos, account ~3 yr old
Inputs used
followers1
owner_typeOrganization
is_verified
owner_loginAntCMS-org
public_repos8
account_age_days1,283
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
26/35Publish recencylatest publish 228 days ago
20/20Version history9 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesantcms/antloader
ecosystemspackagist
any_deprecatedno
min_days_since_publish228

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests4 out of 17 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsautoloader, php, php-autoloader, php-class-autoloader, php-class-map
has_wikiyes
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?

40Weak · 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.5/2.5CI-Tests4 out of 17 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/25 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4
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.

33At 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 config.php-cs-fixer.php, phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
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_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/11 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes12,831
source_files_sampled11
oversized_source_files0

Key facts

3GitHub stars
3contributors
5commits, last 12 months
0days since last push
9releases
1bus factor
0open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-15 15:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests4 out of 17 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/25 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
All dependencies 6

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

RegistryPackageVersionRelation
Packagistcomposer/class-map-generatorindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistpestphp/pestindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistrector/rector2.1.2indirect
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.11.0 — full methodology · metrics wiki.

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