@splunk/dashboard-core — Greenflagged

Core dashboard rendering components for layouts, visualizations, inputs, and action menus

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/react-ui	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/dashboard-definition	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/dashboard-layouts	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/dashboard-search	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/dashboard-ui	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/react-icons	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/ui-utils	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
dependencies	unvetted-dep:@splunk/themes	AI (dependencies): First-party Splunk monorepo sibling package.	ai	2026/07/14
provenance	missing-githead	AI (provenance): Consistent with unchanged provenance direction; internal monorepo publish variance.	ai	2026/07/14
phantom-deps	phantom-dep:@splunk/datasource-utils	AI (phantom-deps): Same-org monorepo dep, not directly imported but expected.	ai	2026/07/14
phantom-deps	phantom-dep:@splunk/visualization-icons	AI (phantom-deps): Same-org monorepo dep, not directly imported but expected.	ai	2026/07/14
bogus-package	bogus-package	AI (bogus-package): Internal enterprise Splunk package; sparse metadata is expected for org-internal npm distributions.	ai	2026/05/29
phantom-deps	phantom-dep:prop-types	AI (phantom-deps): Config-file-only reference; stable false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:@splunk/dashboard-telemetry	AI (phantom-deps): Same @splunk org scope; likely used transitively or conditionally in this monorepo package.	ai	2026/05/25
phantom-deps	phantom-dep:hash-it	AI (phantom-deps): Referenced in config files only; stable false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@splunk/datasources	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for peer/config-only deps in this package.	ai	2026/05/20
phantom-deps	phantom-dep:rxjs	AI (phantom-deps): Referenced in config files only; stable false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@splunk/dashboard-search	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for peer/config-only deps in this package.	ai	2026/05/20

Versions (showing 26 of 26)

Version	Deps	Published
29.8.0	19 / 27	2026-07-21
29.7.0	19 / 27	2026-06-10
29.6.1	19 / 26	2026-07-13
29.6.0	19 / 26	2026-05-06
29.5.3	19 / 26	2026-07-14
29.5.2	19 / 26	2026-04-30
29.5.1	19 / 26	2026-04-24
29.5.0	19 / 26	2026-03-21
29.4.0	19 / 26	2026-02-04
29.3.5	19 / 27	2026-07-13
29.3.4	19 / 27	2025-12-18
29.3.3	19 / 27	2025-12-16
29.3.2	19 / 27	2025-12-11
29.3.1	19 / 27	2025-12-10
29.3.0	19 / 27	2025-11-18
29.2.1	19 / 31	2025-11-20
29.2.0	19 / 31	2025-10-08
29.1.0	23 / 32	2025-08-26
29.0.0	23 / 32	2025-07-23
28.6.4	21 / 31	2026-07-14
28.6.3	21 / 31	2026-04-16
28.6.2	21 / 31	2025-11-24
28.5.1	21 / 31	2026-07-15
28.2.3	21 / 31	2026-07-14
28.2.2	21 / 31	2026-04-14
27.3.2	22 / 29	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.2

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.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.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.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

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.

v27.3.2

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.