Repository navigation
v1.2.0
What's new
- TypeScript scanning:
.ts,.mtsand.ctsfiles are now checked with the same risky-pattern rules as JS and shell files. --jsonoutput: findings are printed as a JSON array of{ file, rule, message }objects ([]when clean), handy for CI. Exit codes are unchanged (0 clean, 1 findings, 2 bad path).- Non-registry dependencies:
package.jsondependencies that bypass the npm registry are flagged:git+https,git+sshandgit://URLs,github:/gitlab:/bitbucket:and bareuser/reposhorthands, tarball and other http(s) URLs,file:andlink:paths. Semver ranges, dist-tags,npm:aliases andworkspace:specs are not flagged. - README documents the new flag and checks;
--versionprints 1.2.0.
Thanks
Huge thanks to @ayushdwivedi-stack for the first community contribution (#4), which closed #1, #2 and #3 in one clean PR. Follow-up checks and docs in #5.
Upgrade
curl -O https://raw.githubusercontent.com/cryptostrapon/npm-install-audit/v1.2.0/audit.js
node audit.js --json ./take-home-task
A clean result is still not proof of safety. Read the code and open unknown repos in a throwaway container or VM.