@splunk/visualizations
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): d3-hierarchy is a standard D3 module supporting the new Treemap visualization. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are bundled Treemap.js/map build output, consistent with new feature. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active Splunk monorepo package; versioned cadence makes dormancy flags unreliable here. | ai | |
| dependencies | unvetted-dep:@splunk/visualization-canvas | AI (dependencies): First-party Splunk dependency matching the package's own version constraint; expected sibling dep. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel runtime is injected by preset; framework-scoped, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:slate-dom | AI (phantom-deps): Peer/transitive of slate-react; declared for hoisting, not directly imported. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 28.8.0 | 47 / 76 | |
| 28.7.0 | 46 / 76 | |
| 28.6.0 | 46 / 73 | |
| 28.5.1 | 42 / 72 | |
| 28.5.0 | 42 / 72 | |
| 27.5.2 | 37 / 72 | |
| 27.5.1 | 37 / 72 | |
| 27.2.3 | 36 / 72 | |
| 27.2.2 | 36 / 72 | |
| 26.4.2 | 33 / 56 | |
| 26.2.2 | 34 / 59 | |
| 25.13.2 | 34 / 65 |
v28.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.