@splunk/themes
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 | encoded-string-file:enterprise/dark.js | AI (source-diff): Base64 string is a PNG image asset embedded via babel-plugin-base64-pngimport; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:enterprise/light.js | AI (source-diff): Base64 string is a PNG image asset embedded via babel-plugin-base64-pngimport; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Splunk SUI packages consistently publish without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 4 / 35 | |
| 1.7.2 | 4 / 40 | |
| 1.7.1 | 4 / 40 | |
| 1.7.0 | 3 / 43 | |
| 1.6.0 | 3 / 42 | |
| 1.5.0 | 3 / 42 | |
| 1.4.1 | 3 / 39 | |
| 1.4.0 | 3 / 39 | |
| 1.3.0 | 3 / 39 | |
| 1.2.1 | 3 / 36 | |
| 1.2.0 | 3 / 36 | |
| 1.1.0 | 3 / 36 | |
| 1.0.1 | 3 / 36 | |
| 1.0.0 | 3 / 36 |
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.