idna-uts46-hx
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/index.cjs | AI (source-diff): Minified rollup/terser output of IDNA/punycode logic; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/index.bundle.js | AI (source-diff): Same minified bundle pattern; content matches documented IDNA processing library. | ai | |
| phantom-deps | phantom-dep:tr46 | AI (phantom-deps): tr46 is bundled via rollup into dist files; not directly imported at runtime. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.1.7 | 1 / 20 | |
| 6.1.6 | 1 / 20 | |
| 6.1.5 | 1 / 20 | |
| 6.1.4 | 1 / 20 | |
| 6.1.3 | 1 / 20 | |
| 6.1.2 | 1 / 20 | |
| 6.1.1 | 1 / 18 | |
| 6.1.0 | 1 / 18 | |
| 6.0.9 | 1 / 18 |
v6.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
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.
v6.1.4
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.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.