It has strong packaging evidence, including tests, a changelog, release notes, and a recent release cadence. The organization-owned repository is active, but no security policy or scanning is present.
77%
Total Score
83
100
94
50
All 12 recent commits came from one contributor, giving the project a single-person maintenance dependency. Organization backing provides some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than evidence of abandonment.
The repository has no security policy. This weakens the project's published process for handling vulnerabilities, although the active repository and documented package reduce the overall concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
glueful/extension-contracts Version ^1.3.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.