The organization backing and recent release notes add useful continuity, while the package remains small and focused. Maintenance is concentrated in one recent contributor, and the workflows use seven unpinned actions with no security policy.
68%
Total Score
63
100
94
67
Only one account has registry publish access. That is normal hygiene for an organization-backed project, but it still represents a narrow publishing path.
One contributor made all commits in the last three months. Organization backing provides some handoff capacity, but no second active contributor is shown.
Only one commit was recorded in the last three months, by one active maintainer. This is evidence of limited recent maintenance, despite the recent registry releases.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a meaningful transparency and maintenance gap.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rapidez/core Version ^5.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.