Replace alias paths with relative paths after typescript compilation.
88%
Total Score
healthy
Healthy: active releases and repository maintenance outweigh concentrated ownership and unpinned workflow actions.
No build attestation or trusted-publisher provenance is present, so consumers have less independent evidence that the registry artifact came from the reviewed source.
The package has a prepare install lifecycle script, which adds install-time behavior and a modest supply-chain review concern, though this signal alone is not severe.
The repository is owned by a user account rather than an organization, so the concentrated contributor activity provides less organizational continuity.
Two contributors were active in the last three months, but one made 30 of 35 commits, leaving maintenance highly concentrated.
The project uses TypeScript and npm scripts for builds, but no security-scanning tooling was detected. This is a modest transparency gap, not evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mylas Version ^2.1.9 | — | — |
globby Version ^11.0.4 | — | — |
chokidar Version ^3.5.3 | — | — |
commander Version ^9.0.0 | — | — |
plimit-lit Version ^1.2.6 | — | — |
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.