@splunk/dashboard-state
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after refactor explains dormancy; established Splunk publisher with clean track record. | ai | |
| source-diff | obfuscated-file:dist/tokenTrace.worker.js | AI (source-diff): Standard minified build artifact from Splunk's dashboard build toolchain; content is readable token-tracing logic. | ai | |
| source-diff | obfuscated-file:module/tokenTrace.worker.js | AI (source-diff): Same minified worker artifact in ESM output directory; not obfuscated, just bundled. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk UI utility; consistent across versions of this package family. | ai | |
| provenance | no-provenance | AI (provenance): Splunk dashboard packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk SDK package; sparse metadata is consistent across the Splunk dashboard package family. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 29.6.0 | 8 / 11 | |
| 29.5.2 | 8 / 11 | |
| 29.5.1 | 8 / 11 | |
| 29.4.0 | 8 / 11 | |
| 29.3.4 | 8 / 11 | |
| 29.3.2 | 8 / 11 | |
| 29.3.1 | 8 / 11 | |
| 29.3.0 | 8 / 11 | |
| 29.2.1 | 8 / 11 | |
| 29.1.0 | 8 / 11 | |
| 29.0.0 | 8 / 11 | |
| 28.6.3 | 8 / 10 | |
| 28.6.2 | 8 / 10 | |
| 28.2.2 | 8 / 10 |
v29.6.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.2
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.1
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.