Minimal module to check if a file is executable.
68%
Total Score
50
100
94
70
50
No build attestation, trusted publisher, or staged publishing evidence is available, leaving the connection between source and published artifact less independently verifiable.
One of two workflows uses pull_request_target, which can increase CI risk when handling untrusted pull requests. No untrusted checkouts or script-injection patterns were detected, reducing the severity.
A prepare install-time script is present, which adds some installation complexity and supply-chain exposure, although the package has no runtime dependencies and the repository shows an ordinary TypeScript build structure.
Only one registry account has publish access. This is a meaningful bus-factor concern for release continuity, even though repository activity shows the package is actively published.
The repository is owned by an individual account rather than an organization. Combined with one registry maintainer and no recent commits, this leaves limited visible continuity beyond the recent 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.