metascope
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/bin/jiti-Bqwg645p.js | AI (source-diff): Minified jiti runtime bundle; readable module-loader code, no malicious indicators. | ai | |
| source-diff | obfuscated-file:dist/bin/shared-DovHaiUj.js | AI (source-diff): Minified shared utility bundle (TOML parser, fs helpers); no malicious indicators. | ai | |
| phantom-deps | phantom-dep:updates | AI (phantom-deps): updates is a dev/tooling dep referenced in config, not a phantom. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): Type-only package; loaded by convention. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): jiti is a runtime loader referenced in config; common pattern for ESM/TS tooling. | ai | |
| phantom-deps | phantom-dep:@types/yargs | AI (phantom-deps): Type-only package; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/plist | AI (phantom-deps): Type-only package; loaded by convention. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): yargs is a CLI dep; likely used indirectly via bin entry, not a direct import. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; loaded by convention, not direct import. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 36 / 18 | |
| 0.8.1 | 36 / 18 | |
| 0.8.0 | 36 / 18 | |
| 0.7.6 | 36 / 18 | |
| 0.7.3 | 37 / 18 | |
| 0.7.1 | 37 / 18 | |
| 0.7.0 | 37 / 18 | |
| 0.6.0 | 37 / 17 | |
| 0.5.0 | 37 / 17 | |
| 0.4.0 | 37 / 17 | |
| 0.3.0 | 36 / 17 |
v0.8.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.