@splunk/dashboard-definition
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish pipeline variance across Splunk monorepo releases; no behavior change. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Bundled build chunks, consistent with build tooling output. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @splunk/dashboard-validation sibling package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for scoped org packages, not a spam indicator. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 29.8.0 | 6 / 7 | |
| 29.7.0 | 6 / 7 | |
| 29.6.1 | 6 / 6 | |
| 29.6.0 | 6 / 6 | |
| 29.5.3 | 6 / 6 | |
| 29.5.2 | 6 / 6 | |
| 29.5.1 | 6 / 6 | |
| 29.5.0 | 6 / 6 | |
| 29.4.0 | 6 / 6 | |
| 29.3.5 | 6 / 6 | |
| 29.3.4 | 6 / 6 | |
| 29.3.3 | 6 / 6 | |
| 29.3.2 | 6 / 6 | |
| 29.3.1 | 6 / 6 | |
| 29.3.0 | 6 / 6 | |
| 29.2.1 | 6 / 6 | |
| 29.2.0 | 6 / 6 | |
| 29.1.0 | 6 / 6 | |
| 29.0.0 | 6 / 6 | |
| 28.6.4 | 6 / 6 | |
| 28.6.3 | 6 / 6 | |
| 28.6.2 | 6 / 6 | |
| 28.5.1 | 6 / 6 | |
| 28.2.3 | 6 / 6 | |
| 28.2.2 | 6 / 6 | |
| 27.3.2 | 7 / 5 |
v29.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.5
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.4
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.3
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.