The package is well documented and tested, with release notes and a clear MIT license. Its small owner base and aging maintenance record make long-term support less certain, while the workflow’s unpinned actions add a modest supply-chain hygiene concern.
60%
Total Score
50
100
94
83
Only one registry account has publishing access. That is a thin operational base for continuity, although the linked repository is also owned by the same individual.
The repository and registry namespace are owned by the same individual, so the package’s source and publication identity align. Individual ownership still means limited organizational redundancy.
The latest registry release was published nearly six years ago, with no releases in the last 12 months. This is a meaningful maintenance concern for a dependency, despite a history of eight releases.
There were no commits from active maintainers in the last three months, and the repository’s last push was about three years ago. This materially raises the risk that fixes and compatibility updates will not arrive promptly.
There were no new or closed issues or pull requests in the last month, with ten issues and two pull requests still open. This is consistent with a currently quiet project.
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.