Version 0.4.0 appears to be a healthy, actively maintained dependency: it has a three-year release history with 5 releases in the last 12 months, recent repository activity, two active contributors, organization backing, appropriate build and dependency tooling, and no deprecation or archival status. The package is well documented and licensed, and its repository clearly matches the package. The main concerns are its still-pre-1.0 version, modest public adoption, lack of a security policy, and incomplete explicit GitHub Actions token-permission declarations, but these do not outweigh the strong maintenance and provenance evidence.
86%
Total Score
100
100
89
80
The repository has 0 stars and 0 forks, indicating limited public adoption; this is a supporting concern rather than a health verdict because maintenance activity is strong.
No repository security policy was found, leaving vulnerability-reporting guidance undocumented; this is a transparency gap but not evidence of abandonment.
Neither workflow declares top-level token permissions, although no workflow has top-level write permissions and one uses job-level permissions; explicit least-privilege configuration would improve supply-chain hygiene.
Version 0.4.0 is not a stable major release, so API compatibility may still evolve, but it is not a prerelease and recent releases have not been prereleases.
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.