@splunk/visualization-encoding
Supply chain provenance
Status for the latest visible version.
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
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 | |
| npm-metadata | no-description | AI (npm-metadata): Established Splunk internal package; missing description is a stable characteristic. | ai | |
| provenance | no-provenance | AI (provenance): Splunk internal publishing pipeline does not use Sigstore provenance; stable across versions. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 28.8.0 | 6 / 5 | |
| 28.7.0 | 6 / 5 | |
| 28.6.0 | 6 / 5 | |
| 28.5.3 | 6 / 5 | |
| 28.5.2 | 6 / 5 | |
| 28.5.1 | 6 / 5 | |
| 28.5.0 | 6 / 5 | |
| 28.4.0 | 6 / 5 | |
| 28.3.0 | 6 / 5 | |
| 28.2.3 | 6 / 5 | |
| 27.5.2 | 6 / 5 | |
| 27.5.1 | 6 / 5 | |
| 27.2.3 | 6 / 10 | |
| 27.2.2 | 6 / 10 | |
| 26.4.2 | 6 / 18 | |
| 26.2.2 | 6 / 18 | |
| 25.13.2 | 6 / 23 |
v28.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.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.
v28.2.3
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.