← Home

@splunk/dynamic-editors

npm
15
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stsuisplunk-tlisplunkerdexa187kova71aprunedadanielsplunkrhesplunk_dashboard_publishercodycoats_splunksplunk-observability-instrumentationdraghunathanjreichardtxhu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 15 of 15)

Version Deps Published
0.45.0 7 / 48
0.44.7 7 / 48
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
0.43.2 7 / 48
0.43.1 7 / 48
0.43.0 7 / 48
0.42.2 7 / 48
0.42.1 7 / 48
0.42.0 7 / 48
0.41.0 7 / 48
0.40.0 7 / 48

v0.45.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.44.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.41.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.40.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.