@splunk/dashboard-event-handlers
Built-in dashboard event handlers for tokens, time ranges, tabs, and custom URLs
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Splunk dashboard packages consistently lack Sigstore provenance; stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Splunk internal scoped package; missing repo/keywords is consistent across the monorepo, not a spam indicator. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-types | AI (dependencies): Same-version monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-utils | AI (dependencies): Same-version monorepo sibling; not an independent risk. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 2 / 4 | |
| 29.5.1 | 2 / 4 | |
| 29.5.0 | 2 / 4 | |
| 29.4.0 | 2 / 4 | |
| 29.3.4 | 2 / 4 | |
| 29.3.3 | 2 / 4 | |
| 29.3.2 | 2 / 4 | |
| 29.3.1 | 2 / 4 | |
| 29.3.0 | 2 / 4 | |
| 29.2.1 | 2 / 4 | |
| 29.2.0 | 2 / 4 | |
| 29.1.0 | 1 / 5 | |
| 29.0.0 | 1 / 5 | |
| 28.6.2 | 1 / 5 |
v29.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.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.
v29.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.