@splunk/visualization-encoding Apache-2.0 2 versions

@splunk/visualization-encoding

npm

Versions

Apache-2.0

License

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

stsuisplunk-tlisplunkerdexa187kova71aprunedadanielsplunkrhesplunk_dashboard_publishercodycoats_splunksplunk-observability-instrumentationdraghunathanjreichardtxhu

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Internal Splunk scoped package; missing metadata is typical for enterprise-internal npm packages.	ai	2026/05/02
npm-metadata	no-description	AI (npm-metadata): Established Splunk internal package; missing description is a stable characteristic.	ai	2026/05/02
provenance	no-provenance	AI (provenance): Splunk internal publishing pipeline does not use Sigstore provenance; stable across versions.	ai	2026/05/02

Versions (showing 2 of 2)

Version	Deps	Published
28.7.0	6 / 5	2026-06-02
28.6.0	6 / 5	2026-04-29

v28.7.0

1 finding

INFO No provenance attestation provenance

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

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.