@splunk/dashboard-presets Apache-2.0 26 versions

@splunk/dashboard-presets

npm

Preset mappings that wire dashboard visualizations, layouts, inputs, event handlers, and data sources

26

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

splunkervtsvetkov-splunksplunk_dashboard_publisher

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@splunk/dashboard-visualizations	AI (dependencies): Official Splunk-scoped sibling package within same monorepo.	ai	2026/07/14
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Referenced via config, common pattern for utility libs.	ai	2026/07/14
publish-pattern	new-deps-added	AI (publish-pattern): New deps are first-party @splunk/* packages, not third-party additions.	ai	2026/07/14
provenance	missing-githead	AI (provenance): Routine monorepo publish variance for this long-running Splunk package, not a compromise indicator.	ai	2026/07/14
phantom-deps	phantom-dep:@splunk/dashboard-utils	AI (phantom-deps): Same-org monorepo dep, declared but not directly imported; consistent pattern.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/visualizations	AI (dependencies): Internal Splunk dependency; consistent with the package's ecosystem context.	ai	2026/05/30
dependencies	unvetted-dep:@splunk/ui-utils	AI (dependencies): Internal Splunk dependency; consistent with the package's ecosystem context.	ai	2026/05/30
dependencies	unvetted-dep:@splunk/dashboard-ui	AI (dependencies): Internal Splunk dependency; consistent with the package's ecosystem context.	ai	2026/05/30
bogus-package	bogus-package	AI (bogus-package): Corporate @splunk scoped package; missing repo/keywords is normal for enterprise monorepo artifacts.	ai	2026/05/28
phantom-deps	phantom-dep:@splunk/react-icons	AI (phantom-deps): Same-org scope; likely re-exported or used indirectly via bundled output in this monorepo package.	ai	2026/05/24
phantom-deps	phantom-dep:@splunk/dashboard-icons	AI (phantom-deps): Same-org scope; consistent with monorepo indirect usage pattern.	ai	2026/05/24

Versions (showing 26 of 26)

Version	Deps	Published
29.8.0	12 / 14	2026-07-21
29.7.0	12 / 14	2026-06-10
29.6.1	11 / 6	2026-07-13
29.6.0	11 / 6	2026-05-06
29.5.3	11 / 6	2026-07-14
29.5.2	11 / 6	2026-04-30
29.5.1	11 / 6	2026-04-24
29.5.0	11 / 6	2026-03-21
29.4.0	11 / 6	2026-02-04
29.3.5	10 / 6	2026-07-13
29.3.4	10 / 6	2025-12-18
29.3.3	10 / 6	2025-12-16
29.3.2	10 / 6	2025-12-11
29.3.1	10 / 6	2025-12-10
29.3.0	10 / 6	2025-11-18
29.2.1	10 / 6	2025-11-20
29.2.0	10 / 6	2025-10-08
29.1.0	11 / 6	2025-08-26
29.0.0	11 / 6	2025-07-23
28.6.4	11 / 5	2026-07-14
28.6.3	11 / 5	2026-04-16
28.6.2	11 / 5	2025-11-24
28.5.1	11 / 5	2026-07-15
28.2.3	11 / 5	2026-07-14
28.2.2	11 / 5	2026-04-14
27.3.2	13 / 4	2026-07-14

v29.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.3.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.6.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.6.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.

v28.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.5.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.

v28.2.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.

v28.2.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.

v27.3.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.