← Home

shimmer

npm Repository Homepage

Safe(r) monkeypatching for JavaScript.

14
Versions
BSD-2-Clause
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

othiym23

Keywords

monkeypatchswizzlewrappingdangerhmmshim

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:aoaioxxysz.net AI (email-domain): Package is 13+ years old with a well-established publisher (othiym23). The lapsed personal domain is a theoretical hijack risk but no active compromise is indicated. Stable false-positive for this package. ai

Versions (showing 14 of 14)

Version Deps Published
1.2.1 0 / 3
1.2.0 0 / 3
1.1.1 0 / 3
1.1.0 0 / 3
1.0.0 0 / 2
0.9.2 0 / 2
0.9.1 0 / 2
0.9.0 0 / 2
0.8.1 0 / 2
0.8.0 0 / 2
0.7.3 0 / 2
0.7.1 0 / 2
0.6.1 0 / 2
0.6.0 0 / 2

v1.2.1

2 findings
HIGH Unclaimed maintainer email domain: aoaioxxysz.net email-domain

Maintainer email '[email protected]' uses domain 'aoaioxxysz.net' 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.

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.9.2

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.1

2 findings
HIGH Unclaimed maintainer email domain: aoaioxxysz.net email-domain

Maintainer email '[email protected]' uses domain 'aoaioxxysz.net' 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.6.1

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.6.0

2 findings
HIGH Unclaimed maintainer email domain: aoaioxxysz.net email-domain

Maintainer email '[email protected]' uses domain 'aoaioxxysz.net' 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. Only ~12% of npm packages have provenance, so this is common but not ideal.