@dxtmisha/wiki
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/wikiDescriptions-BxZP798_.js | AI (source-diff): File is a large data bundle of UI component descriptions, not obfuscated code; long lines are structured text arrays. | ai | |
| source-diff | obfuscated-file:dist/wikiDescriptions-CRalqVE2.js | AI (source-diff): Vite-bundled data file with plain text UI descriptions; long lines are minified JSON-like arrays, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/wikiDescriptions-n3cFkYRZ.js | AI (source-diff): Vite-bundled data file with readable UI component descriptions; long lines from minification, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/wikiDescriptions-7XaHU3Yk.js | AI (source-diff): Vite-bundled dist file with readable component description data; long lines from minification, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/wikiDescriptions-Dbkpa2Je.js | AI (source-diff): Vite-bundled data file with plain UI description strings; long lines are minified JSON-like arrays, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/wikiDescriptions-CJv5fdyX.js | AI (source-diff): File is a Vite-bundled data chunk with readable plain-text content; long lines are from large string arrays, not obfuscation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.67.1 | 0 / 0 | |
| 0.67.0 | 0 / 0 | |
| 0.65.0 | 0 / 0 | |
| 0.64.0 | 0 / 0 | |
| 0.59.1 | 0 / 0 | |
| 0.59.0 | 0 / 0 | |
| 0.57.6 | 0 / 0 | |
| 0.57.4 | 0 / 0 | |
| 0.57.3 | 0 / 0 | |
| 0.57.1 | 0 / 0 | |
| 0.57.0 | 0 / 0 | |
| 0.56.0 | 0 / 0 | |
| 0.39.8 | 0 / 0 |
v0.67.1
2 findingsNewly 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.67.0
2 findingsNewly 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.65.0
2 findingsNewly 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.64.0
2 findingsNewly 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.59.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
2 findingsNewly 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.57.6
2 findingsNewly 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.57.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.1
2 findingsNewly 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.57.0
2 findingsNewly 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.56.0
2 findingsNewly 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.39.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.