Load modules according to tsconfig paths in webpack.
67%
Total Score
50
100
90
63
50
No build attestation or trusted-publisher provenance is available, leaving publication origin and build reproducibility less transparent. This is a hygiene gap, not evidence that the release is unsafe.
A prepare lifecycle script is present. This adds install-time build behavior that merits awareness, but the signal alone does not show that it is unsafe or unusually complex.
The repository is owned by an individual account rather than an organization, so there is no provided evidence of organizational backing. This modestly increases continuity risk but is not an abandonment verdict.
The package has existed since July 2017 with 33 releases, but its latest release was about 22 months ago and there were no releases in the last 12 months. This supports maturity but raises maintenance concerns.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with roughly 22 months since the latest release. The repository is not archived, but current maintenance capacity appears limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chalk Version ^4.1.0 | — | — |
tapable Version ^2.2.1 | — | — |
tsconfig-paths Version ^4.1.2 | — | — |
enhanced-resolve Version ^5.7.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.