@splunk/dashboard-layouts
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): Minor publish-env variance across trusted Splunk monorepo releases, no malicious indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): prop-types is a standard, well-known React utility dep. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are build artifacts (JS bundles + source maps); expected pattern for this Splunk dashboard package. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a disqualifier for established packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk enterprise package; sparse README and no public repo URL is expected for this org's packages. | ai | |
| phantom-deps | phantom-dep:@splunk/datasource-utils | AI (phantom-deps): Same org scope; likely referenced in config/types only, stable false positive. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-definition | AI (dependencies): Splunk dashboard monorepo sibling; co-versioned at 29.5.2. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): Splunk-owned ecosystem dependency; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is declared in dependencies and used in the package; phantom-dep heuristic misfires here. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Splunk-owned ecosystem dependency; stable false positive for this monorepo package. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): Splunk-owned ecosystem dependency; stable false positive for this monorepo package. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-ui | AI (dependencies): Splunk dashboard monorepo sibling; co-versioned at 29.5.2. | ai | |
| dependencies | unvetted-dep:@splunk/visualizations | AI (dependencies): Splunk-owned visualization package; stable false positive for this monorepo package. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-state | AI (dependencies): Splunk dashboard monorepo sibling; co-versioned at 29.5.2. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 29.8.0 | 19 / 23 | |
| 29.7.0 | 19 / 23 | |
| 29.6.1 | 20 / 20 | |
| 29.6.0 | 20 / 20 | |
| 29.5.3 | 20 / 20 | |
| 29.5.2 | 20 / 20 | |
| 29.5.1 | 20 / 20 | |
| 29.3.5 | 20 / 19 | |
| 29.3.3 | 20 / 19 | |
| 29.3.0 | 20 / 19 | |
| 29.2.1 | 19 / 24 | |
| 29.2.0 | 19 / 24 | |
| 29.1.0 | 20 / 24 | |
| 29.0.0 | 20 / 24 | |
| 28.6.4 | 20 / 23 | |
| 28.6.3 | 20 / 23 | |
| 28.5.1 | 20 / 23 | |
| 28.2.3 | 20 / 23 | |
| 28.2.2 | 20 / 23 | |
| 27.3.2 | 17 / 22 |
v29.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.1
1 finding[Accepted risk] Package 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.
v27.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.