@washingtonpost/wpds-assets
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/assets/index.181a0bcc.js | AI (source-diff): Vite build artifact (React prod bundle + SVG icons); minification is expected for this design-system assets package. | ai | |
| source-diff | obfuscated-file:dist/assets/index.3961a039.js | AI (source-diff): Standard Vite/React minified bundle for a WP icon library; no malicious patterns in sample. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established 96-version WP design system; gaps between releases are normal for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.16.3 | 2 / 15 | |
| 2.15.2 | 2 / 15 | |
| 2.15.1 | 2 / 15 | |
| 2.15.0 | 2 / 15 | |
| 2.14.0 | 2 / 15 | |
| 2.13.1 | 2 / 15 | |
| 2.13.0 | 2 / 15 | |
| 2.12.0 | 2 / 15 | |
| 2.11.4 | 2 / 15 |
v2.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.2
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.
v2.15.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.
v2.15.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.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.