Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 23:14 UTC

goaop / framework

:gem: Go! AOP PHP - modern aspect-oriented framework for the new level of software development

PHPMIT★ 1,665 stars⑂ 165 forkssince Feb 2011View on GitHub ↗

goaop/framework holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on Security (55/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

8 followers13 public repossince May 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistgoaop/framework3.1.125,22338108 days agophpaoplibraryaspect

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9/36Commit cadence13/52 weeks with commits
18/18Commit volume159 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year159
human_commit_share
days_since_last_push0
active_weeks_last_year13
How it's scored
27/27Ships releases24 releases published
36/36Release recencylatest release 65 days ago
12.6/27Release cadencea release every ~357.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count24
latest_release_tag3.1.1
releases_from_tagsno
days_since_latest_release65
mean_days_between_releases357.9
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?

67Good · 17% of overall
How it's scored
52.3/60Stars1,665 stars
18.5/25Forks165 forks
10.6/15Watchers81 watchers
Inputs used
forks165
stars1,665
watchers81
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
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
58.7/80Monthly downloads25,223 downloads/month across packagist
10.5/20Registry dependents37 packages depend on it
Inputs used
packagesgoaop/framework
dependents37
ecosystemspackagist
total_downloads4,097,162
monthly_downloads25,223
unverified_packages_excluded

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.2/22.5Commit distributiontop contributor authored 90% of commits
13.5/13.5Contributor breadth39 contributors
10/10OpenSSF Scorecard: Contributorsproject has 24 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled39
top_contributor_share0.9
How it's scored
41.6/42Issue resolution99% of issues closed
25.5/30PR acceptance211/248 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/9 approved changesets -- score normalized to 0
Inputs used
merged_prs211
open_issues3
closed_issues329
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.991
closed_unmerged_prs37
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
6.9/25Owner reach8 followers of goaop
20.3/25Track record13 public repos, account ~11 yr old
Inputs used
followers8
owner_typeOrganization
is_verified
owner_logingoaop
public_repos13
account_age_days4,075
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 108 days ago
20/20Version history38 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgoaop/framework
ecosystemspackagist
any_deprecatedno
min_days_since_publish108

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://go.aopphp.com
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsaspect-oriented-framework, php, aop, framework, interceptor, aspect-oriented-programming
has_wikino
homepagehttps://go.aopphp.com
docs_sitehttps://go.aopphp.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests13 out of 13 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/7.5Code-ReviewFound 0/9 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 24 contributing companies or organizations
0/10Dangerous-Workflowno data
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 7 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_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.5
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.

65Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, src/Aop/AGENTS.md, src/Core/AGENTS.md, src/Instrument/AGENTS.md, src/Proxy/AGENTS.md, tests/AGENTS.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesAGENTS.md, src/Aop/AGENTS.md, src/Core/AGENTS.md, src/Instrument/AGENTS.md, src/Proxy/AGENTS.md, tests/AGENTS.md
agent_instruction_max_bytes3,985
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
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/323 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes31,275
source_files_sampled323
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesdemos, example
Inputs used
example_dirsdemos, example
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,665GitHub stars
39contributors
159commits, last 12 months
0days since last push
24releases
1bus factor
3open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-18 23:13 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/9 approved changesets -- score normalized to 0
10Contributorsproject has 24 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 7 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 4
RegistryPackageVersion constraintManifest
Packagistgoaop/parser-reflection4.x-devcomposer.json
Packagistgoaop/dissect^4.0composer.json
Packagistnikic/php-parser^5.0composer.json
Packagistsymfony/finder^7.4 || ^8.0composer.json
All dependencies 15

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

RegistryPackageVersionRelation
Packagistgoaop/dissectdirect
Packagistgoaop/parser-reflectiondirect
Packagistnikic/php-parserdirect
Packagistsymfony/finderdirect
Packagistadlawson/vfsindirect
Packagistdoctrine/ormindirect
Packagistext-tokenizerindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/consoleindirect
Packagistsymfony/filesystemindirect
Packagistsymfony/processindirect
Packagisttracy/tracyindirect
Packagistwebmozart/globindirect
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.14.0 — full methodology · metrics wiki.

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