react-addons-transition-group
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-removed | AI (maintainer-change): Removal of graue is part of the documented React team reorganization in 2017; no evidence of malicious takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-transition-group is the official standalone replacement for this addon; adding it as a dependency is the documented migration path for react-addons-transition-group. | ai | |
| provenance | publisher-changed | AI (provenance): zpao and tomocchino are both Facebook/React core team members; this is a legitimate internal team transition for the official react-addons-* package family. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fb and tomocchino are official Facebook/React team accounts; maintainer additions reflect legitimate org-level ownership consolidation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): react-addons-* packages are published in batches aligned with React releases; dormancy between releases is expected and not indicative of takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): react-addons-transition-group is an intentionally thin shim/re-export package; tiny payload and minimal README are by design for this package family. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 15.6.2 | 1 / 0 | |
| 15.6.0 | 1 / 0 | |
| 15.5.2 | 2 / 0 | |
| 15.5.1 | 2 / 0 | |
| 15.5.0 | 2 / 0 | |
| 15.4.2 | 2 / 0 | |
| 15.4.1 | 0 / 0 | |
| 15.4.0 | 0 / 0 | |
| 15.3.2 | 0 / 0 | |
| 15.3.1 | 0 / 0 | |
| 15.3.0 | 0 / 0 | |
| 15.2.1 | 0 / 0 | |
| 15.2.0 | 0 / 0 | |
| 15.1.0 | 0 / 0 | |
| 15.0.2 | 0 / 0 | |
| 15.0.1 | 0 / 0 | |
| 15.0.0 | 0 / 0 |
v15.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.6.0
2 findingsThis version was published by a different npm account than previous versions on 2017-06-14. 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.
v15.5.2
2 findingsThis version was published by a different npm account than previous versions on 2017-04-09. 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.
v15.5.1
2 findingsThis version was published by a different npm account than previous versions on 2017-04-07. 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.
v15.5.0
2 findingsThis version was published by a different npm account than previous versions on 2017-03-31. 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.
v15.4.2
2 findingsThis version was published by a different npm account than previous versions on 2017-01-06. 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.
v15.4.1
2 findingsThis version was published by a different npm account than previous versions on 2016-11-23. 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.
v15.4.0
2 findingsThis version was published by a different npm account than previous versions on 2016-11-16. 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.
v15.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.