Resolve aliased dependency paths using a RequireJS config
77%
Total Score
83
100
67
50
No build attestation or trusted-publisher provenance is available. The package remains adoptable, but its publication chain is less transparent.
One contributor made all 2 commits in the last 3 months, giving the project a concentrated recent commit base. Organization ownership partly offsets handoff risk, but does not remove it.
The repository has no security policy. This is a minor transparency gap for reporting vulnerabilities, not evidence that the package is unsafe.
All 3 workflows use read-only permissions and the audit found no dangerous sinks or findings, but all 7 action references are unpinned. That leaves avoidable workflow supply-chain drift despite otherwise restrained permissions.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
commander Version ^14.0.3 | — | — |
requirejs Version ^2.3.8 | — | — |
requirejs-config-file Version ^4.0.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.