react-addons-css-transition-group MIT 17 versions

react-addons-css-transition-group

npm Repository Homepage

The code in this package has moved. We recommend you to use `CSSTransitionGroup` from [`react-transition-group`](https://github.com/reactjs/react-transition-group) instead.

17

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sophiebitstrueadmgaearonbrianvaughnfb

Keywords

reactreact-addon

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): fb and gaearon are legitimate Facebook/React maintainers, not spam publishers. Tiny payload is expected for this official React shim package that re-exports react-transition-group.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): sophiebits (Sophie Alpert) is a known React core team member; transition from gaearon is a legitimate internal Facebook/React team publishing reorganization in 2017.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): sophiebits is a well-known React core team member; addition reflects legitimate React team publishing consolidation.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of multiple Facebook React team members reflects a known 2017 React team npm publishing reorganization, not a takeover.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by publish is consistent with React team's practice of publishing final addon versions during the React 15.x maintenance period.	ai	2026/04/23

Versions (showing 17 of 17)

Version	Deps	Published
15.6.2	1 / 0	2017-09-26
15.6.0	1 / 0	2017-06-14
15.5.2	2 / 0	2017-04-09
15.5.1	2 / 0	2017-04-07
15.5.0	2 / 0	2017-03-31
15.4.2	2 / 0	2017-01-06
15.4.1	0 / 0	2016-11-23
15.4.0	0 / 0	2016-11-16
15.3.2	0 / 0	2016-09-19
15.3.1	0 / 0	2016-08-19
15.3.0	0 / 0	2016-07-29
15.2.1	0 / 0	2016-07-08
15.2.0	0 / 0	2016-07-01
15.1.0	0 / 0	2016-05-20
15.0.2	0 / 0	2016-04-30
15.0.1	0 / 0	2016-04-08
15.0.0	0 / 0	2016-04-07

v15.6.2

2 findings

HIGH Publisher changed: gaearon → sophiebits (on 2017-09-26) provenance

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

v15.6.0

1 finding

LOW No provenance attestation provenance

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

v15.5.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: brianvaughn → gaearon (on 2017-04-09) provenance

[Accepted risk] This 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.

v15.5.1

1 finding

LOW No provenance attestation provenance

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

v15.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gaearon → brianvaughn (on 2017-03-31) provenance

[Accepted risk] This 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.

v15.4.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: spicyj → gaearon (on 2017-01-06) provenance

[Accepted risk] This 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.

v15.4.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tomocchino → spicyj (on 2016-11-23) provenance

[Accepted risk] This 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.

v15.4.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: zpao → tomocchino (on 2016-11-16) provenance

[Accepted risk] This 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.

v15.3.2

1 finding

LOW No provenance attestation provenance

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

v15.3.1

1 finding

LOW No provenance attestation provenance

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

v15.3.0

1 finding

LOW No provenance attestation provenance

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

v15.2.1

1 finding

LOW No provenance attestation provenance

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

v15.2.0

1 finding

LOW No provenance attestation provenance

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

v15.1.0

1 finding

LOW No provenance attestation provenance

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

v15.0.2

1 finding

LOW No provenance attestation provenance

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

v15.0.1

1 finding

LOW No provenance attestation provenance

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

v15.0.0

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.