The repository has no security policy, and its workflow does not declare top-level token permissions. Its organization backing, long history, tests, and recent release notes provide substantial maintenance evidence.
82%
Total Score
88
100
94
80
All seven recent commits came from one contributor, creating concentration risk. The organization-owned repository provides some handoff capacity, but no second recent contributor is shown.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning reduces assurance modestly without indicating abandonment.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a widely used library.
The CI workflow does not declare top-level token permissions. Although no write permissions were detected, explicitly limiting the token would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.