react-shallow-renderer
React package for shallow rendering.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transfer to known React ecosystem maintainers (ljharb, NMinhNguyen, trueadm/Dominic Gannaway). Well-documented transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original maintainer davidmarkclements removed as part of legitimate ownership transfer to React team affiliates. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): react-is is consumed in rollup-built bundles (cjs/esm/umd), not directly imported in source files. Normal for bundled packages. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from minh.nguyen to gaearon (Dan Abramov, React core team) is a well-documented legitimate maintainer transition. | ai | |
| phantom-deps | phantom-dep:object-assign | AI (phantom-deps): object-assign is consumed in rollup-built bundles, not directly imported in source. Normal for bundled packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): brianvaughn and gaearon are React core team members; adding them to a React ecosystem package is expected. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; no provenance is normal for this era of publishing. | ai | |
| provenance | missing-githead | AI (provenance): Publisher is the repo owner (NMinhNguyen); missing gitHead reflects local publish, not a security concern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 16.15.0 | 2 / 31 | |
| 16.14.1 | 2 / 31 | |
| 16.14.0 | 2 / 31 | |
| 16.13.1 | 2 / 31 | |
| 16.13.0 | 2 / 31 | |
| 16.12.0 | 3 / 21 | |
| 1.1.4 | 2 / 1 | |
| 1.1.3 | 2 / 1 | |
| 1.1.2 | 2 / 1 | |
| 1.1.1 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 |
v16.15.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-06. This could indicate a legitimate maintainer transition or an account compromise.
v16.14.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: minh.nguyen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.14.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.13.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: minh.nguyen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.13.0
4 findingsAll previous maintainers (davidmarkclements) were replaced by new maintainers (ljharb, minh.nguyen, trueadm). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: minh.nguyen.
This version was published by a different npm account than previous versions on 2020-02-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.12.0
4 findingsAll previous maintainers (davidmarkclements) were replaced by new maintainers (minh.nguyen). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: minh.nguyen.
This version was published by a different npm account than previous versions on 2020-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.