← Home

@stdlib/utils-copy

Copy or deep clone a value to an arbitrary depth.

2
Versions
Apache-2.0
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

stdlib-botkgryteplaneshifterrreusser

Keywords

stdlibstdutilsstdutilutilitiesutilsutilcopycpclonedeepdeepcopydeepcloneshallowshallowcopyarrayobjectdateregexptyped arraysetmaperrorerruriurierrorsyntaxsyntaxerrorreferencereferenceerrortypetypeerrorevalevalerrorrangerangeerror

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): stdlib packages consistently lack provenance attestation; stable false positive for this publisher. ai
dependencies unvetted-dep:@stdlib/assert-is-error AI (dependencies): Sibling stdlib package; same publisher and release cadence. ai
dependencies unvetted-dep:@stdlib/buffer-from-buffer AI (dependencies): Sibling stdlib package; same publisher and release cadence. ai
dependencies unvetted-dep:@stdlib/utils-property-names AI (dependencies): Sibling stdlib package; same publisher and release cadence. ai
dependencies unvetted-dep:@stdlib/utils-regexp-from-string AI (dependencies): Sibling stdlib package; same publisher and release cadence. ai
dependencies unvetted-dep:@stdlib/utils-property-descriptor AI (dependencies): Sibling stdlib package; same publisher and release cadence. ai

Versions (showing 2 of 2)

Version Deps Published
0.2.3 26 / 0
0.2.2 26 / 0

v0.2.2

1 finding
INFO No provenance attestation provenance

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