← Home

not-so-shallow

npm Repository Homepage

A less shallow `only-shallow`

3
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

sotojuan

Keywords

deeperdeepestdeepEqualshallowequalequalitystrict

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): buffer-equals is a well-established, benign npm package consistent with this package's deepEqual comparison purpose. Not a suspicious dependency. ai
provenance no-provenance AI (provenance): Package is 10 years old and predates Sigstore provenance; no CI/CD pipeline change expected for this legacy utility. ai

Versions (showing 3 of 3)

Version Deps Published
0.1.4 1 / 4
0.1.3 1 / 4
0.1.2 1 / 4

v0.1.4

2 findings
HIGH Unclaimed maintainer email domain: juansoto.me email-domain

Maintainer email '[email protected]' uses domain 'juansoto.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v0.1.3

2 findings
HIGH Unclaimed maintainer email domain: juansoto.me email-domain

Maintainer email '[email protected]' uses domain 'juansoto.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v0.1.2

2 findings
HIGH Unclaimed maintainer email domain: juansoto.me email-domain

Maintainer email '[email protected]' uses domain 'juansoto.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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