Type check values
82%
Total Score
healthy
Healthy release with a long maintenance history, though recent work is concentrated in one contributor and workflow actions are unpinned.
No build attestation or trusted-publisher provenance is recorded, leaving publication origin less verifiable than it could be; the long release history partly offsets this gap.
A prepare install-time script is present, adding build or installation behavior that consumers should account for, but this signal alone does not show unsafe behavior.
The repository is owned by a user rather than an organization, so the single active contributor and single registry maintainer represent a genuine concentration of maintenance responsibility.
One contributor made 100% of the single recent commit, leaving maintenance dependent on one active person rather than a broader contributor base.
Only 1 commit was recorded in the last 3 months, so current development activity is light despite the recent push and continuing release history.
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.