Workflow dependencies are unpinned and the repository has no security policy. Clear upgrade notes, a maintained organization-owned project, and repository tests improve transparency and adoption confidence.
68%
Total Score
75
100
88
75
The package is over 11 years old but has only 3 releases, with a median interval of about 5.4 years; one release in the last 12 months shows some recent activity but a sparse cadence remains a maintenance concern.
There were no commits and no active maintainers in the last 3 months. Although a recent release shows the project is not abandoned outright, the current activity gap lowers maintenance confidence.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and supply-chain hygiene gap rather than evidence of unsafe behavior.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for consumers of an access-control library.
Both workflows were analyzed cleanly with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 5 action references are unpinned, so workflow inputs are less reproducible and less resistant to upstream changes.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
ray/di Version ~2.0 | — | — |
laminas/laminas-permissions-acl Version ~2.5 | — | — |
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.