@splunk/dynamic-editors
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): Internal Splunk ecosystem dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): Internal Splunk ecosystem dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk ecosystem dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): Internal Splunk ecosystem dependency; expected for this package. | ai | |
| phantom-deps | phantom-dep:@uiw/react-md-editor | AI (phantom-deps): Package is declared in dependencies; phantom-dep is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.44.6 | 7 / 48 | |
| 0.44.5 | 7 / 48 | |
| 0.44.4 | 7 / 48 | |
| 0.44.3 | 7 / 48 | |
| 0.44.2 | 7 / 48 |
v0.44.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.