Check whether a request can be retried based on the `error.code`
68%
Total Score
50
100
89
83
The repository is owned by an individual rather than an organization, so the project has no demonstrated organizational backing to offset the thin recent activity.
The package has seven releases over about 10 years, but none in the last five years. That long release gap lowers confidence in ongoing maintenance, despite the package's long history.
The repository shows zero commits and zero active maintainers in the last three months. This is consistent with a mature, small package but provides little evidence of current maintenance capacity.
The repository reports no build tool or security scanning tool. For this small package that is a modest transparency and maintenance gap, not a severe risk.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, injection findings, or broad top-level write permissions. However, both action references are unpinned, leaving avoidable version-drift and supply-chain exposure.
We didn't find any vulnerabilities for this package.
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.