Healthy and suitable to depend on. It has a long release history, current release notes, a maintained non-archived repository, tests in the source project, and safe workflow checks; the main caveat is that recent commits come from one contributor and workflows do not declare top-level permissions.
82%
Total Score
75
100
100
67
One contributor made all 12 commits in the last 3 months, creating a concentrated recent maintenance dependency. Organization backing provides some handoff capacity, but no second recent contributor is shown.
There were 12 commits in the last 3 months, so development is active, but all recent commits came from one maintainer, limiting resilience if that person becomes unavailable.
No security policy was found, which weakens the project's documented process for receiving and handling vulnerability reports.
Both workflows omit top-level token permissions and neither declares read-only permissions. No workflow requests top-level write access, but explicit least-privilege configuration is still missing.
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.