← Home

react-side-effect

npm Repository Homepage

Create components whose prop changes map to a global side effect

19
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

gaearonlourd

Keywords

reactcomponentsideeffect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Known legitimate maintainer transition from gaearon to lourd in Jan 2017; well-documented in the React ecosystem. No compromise indicators. ai
maintainer-change maintainer-added AI (maintainer-change): lourd is a known React ecosystem contributor; this is a legitimate handoff from Dan Abramov, stable for this package. ai
publish-pattern new-deps-added AI (publish-pattern): exenv and shallowequal are well-known benign React ecosystem packages, replacing fbjs. No malicious signal. ai

Versions (showing 19 of 19)

Version Deps Published
2.1.2 0 / 23
2.1.1 0 / 23
2.1.0 0 / 23
2.0.0 1 / 26
1.2.0 1 / 25
1.1.5 2 / 24
1.1.4 2 / 24
1.1.3 2 / 15
1.1.2 2 / 15
1.1.1 2 / 15
1.1.0 2 / 7
1.0.2 1 / 7
1.0.1 1 / 0
1.0.0 1 / 0
0.3.2 1 / 0
0.3.1 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.0 0 / 0

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
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.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

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

2 findings
HIGH Publisher changed: gaearon → lourd (on 2017-01-08) provenance

This version was published by a different npm account than previous versions on 2017-01-08. 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.

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

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.