deap
extend and merge objects, deep or shallow
1
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
bmharrisprestaul
Keywords
extendmergemixindeepshallowclone
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): prestaul (Matt Dunlap) was already a listed contributor in package.json before the transfer; this is a documented maintainer handoff, not a suspicious account change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Small stable utility library; dormancy is consistent with maturity. Version diff shows no material changes, confirming benign maintenance release. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 0 / 4 |
v1.0.1
2 findings
HIGH
Publisher changed: bmharris → prestaul (on 2018-03-05)
provenance
This version was published by a different npm account than previous versions on 2018-03-05. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.