Install package programmatically.
82%
Total Score
88
100
89
80
100
The artifact and repository include a README, while tests and a changelog are absent from both. The GitHub Releases setup provides some release transparency, but the missing tests leave less evidence of regression coverage.
All 5 recent commits came from one contributor, creating a real single-person continuity risk. The organization-owned repository provides some ability to hand maintenance off, so this is caution rather than a severe abandonment signal.
The repository uses TypeScript, Vite, and npm scripts for builds, but no security scanning tools were detected. Standard build tooling supports maintainability, while the missing scanning is a modest transparency gap.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This lowers transparency but is not by itself evidence that the package is unsafe to depend on.
One workflow lacks top-level token permissions, while the other declares read-only permissions and neither declares top-level write access. The incomplete restriction is a minor workflow-hygiene gap, not a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tinyexec Version ^1.3.1 | — | — |
package-manager-detector Version ^1.8.0 | — | — |
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.