← Home

@splunk/visualizations-shared

npm
20
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

splunkervtsvetkov-splunksplunk_dashboard_publisher

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@loki/create-async-callback AI (dependencies): Loki visual testing utility; matches loki devDependency already present and consistent with storybook test toolchain. ai
dependencies unvetted-dep:@splunk/themes AI (dependencies): Same-org Splunk dependency; consistent with this package's ecosystem. ai
dependencies unvetted-dep:@splunk/react-ui AI (dependencies): Same-org Splunk dependency; consistent with this package's ecosystem. ai
dependencies unvetted-dep:@splunk/ui-utils AI (dependencies): Same-org Splunk dependency; consistent with this package's ecosystem. ai
dependencies unvetted-dep:@splunk/react-icons AI (dependencies): Same-org Splunk dependency; consistent with this package's ecosystem. ai
dependencies unvetted-dep:@splunk/moment AI (dependencies): Same-org Splunk dependency; consistent with this package's ecosystem. ai
phantom-deps phantom-dep:element-resize-detector AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:@splunk/react-icons AI (phantom-deps): Same-org scope; likely re-exported or config-only reference; stable false positive. ai
phantom-deps phantom-dep:prop-types AI (phantom-deps): Referenced in config/type files only; stable false positive for this Splunk monorepo package. ai

Versions (showing 20 of 20)

Version Deps Published
28.6.0 13 / 16
28.5.3 13 / 16
28.5.2 13 / 16
28.5.1 13 / 16
28.5.0 13 / 16
28.4.0 13 / 16
28.3.0 13 / 16
28.2.3 13 / 16
28.2.2 13 / 16
28.2.1 13 / 16
28.2.0 13 / 16
28.1.0 13 / 16
28.0.0 13 / 16
27.5.2 12 / 15
27.5.1 12 / 15
27.2.3 12 / 15
27.2.2 12 / 15
26.4.2 12 / 15
26.2.2 10 / 16
25.13.2 10 / 24

v28.6.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.5.3

1 finding
LOW No provenance attestation provenance

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

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

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.5.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.4.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.3.0

1 finding
LOW No provenance attestation provenance

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

v28.2.3

1 finding
LOW No provenance attestation provenance

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

v28.2.2

1 finding
LOW No provenance attestation provenance

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

v28.2.1

1 finding
LOW No provenance attestation provenance

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

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

v27.5.2

1 finding
LOW No provenance attestation provenance

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

v27.5.1

1 finding
LOW No provenance attestation provenance

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

v27.2.3

1 finding
LOW No provenance attestation provenance

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

v27.2.2

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.

v26.4.2

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.

v26.2.2

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.

v25.13.2

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.