create-react-class
Legacy API for creating React components.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): object-assign is a canonical, widely-trusted ES6 polyfill; its addition is consistent with this legacy React package's purpose and poses no supply-chain risk. | ai | |
| provenance | missing-githead | AI (provenance): Legacy facebook/react monorepo package; missing gitHead reflects historical publish environment, not a security concern for this well-established package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former React team members; part of the same documented 2017 Facebook/React team reorganization. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from gaearon to sophiebits is a documented React team change in 2017; sophiebits is a well-known React core team member with strong track record. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2017, before npm provenance attestation existed. Not a meaningful risk signal for this package. | ai | |
| phantom-deps | phantom-dep:loose-envify | AI (phantom-deps): loose-envify is legitimately used as a browserify transform (declared in browserify.transform config); not a direct import but a valid runtime dependency. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (sophiebits, trueadm, fb) are all known Facebook/React team accounts; legitimate org-level transition. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 15.7.0 | 2 / 5 | |
| 15.6.3 | 3 / 5 | |
| 15.6.2 | 3 / 5 | |
| 15.6.0 | 3 / 5 | |
| 15.5.4 | 3 / 4 | |
| 15.5.3 | 3 / 4 | |
| 15.5.2 | 2 / 4 | |
| 15.5.1 | 1 / 4 | |
| 15.5.0 | 1 / 4 | |
| 1.2.4 | 3 / 2 | |
| 1.2.3 | 3 / 2 | |
| 1.2.2 | 3 / 2 | |
| 1.2.1 | 3 / 2 | |
| 1.2.0 | 3 / 2 | |
| 1.1.1 | 3 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 2 |
v15.6.3
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 2018-01-30. This could indicate a legitimate maintainer transition or an account compromise.
v15.6.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gaearon.
v15.5.4
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: flarnie.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-13. This could indicate a legitimate maintainer transition or an account compromise.
v15.5.3
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gaearon.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-09. This could indicate a legitimate maintainer transition or an account compromise.
v15.5.2
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: acdlite.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acdlite.
v15.5.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acdlite.
[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.