prop-types
Runtime type checking for React props and similar objects.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): gaearon (Dan Abramov) is a React core team member; publishing a Facebook-owned package is expected and legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2018, before Sigstore provenance existed. Stable for this package version. | ai | |
| provenance | missing-githead | AI (provenance): ljharb routinely publishes from local env without gitHead; consistent pattern across his 232+ packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): fb and gaearon are Facebook/Dan Abramov accounts — core React maintainers, not spam. README links to React docs. | ai | |
| phantom-deps | phantom-dep:loose-envify | AI (phantom-deps): loose-envify is used as a browserify transform (config reference), not a direct import — phantom-dep is expected. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 15.8.1 | 3 / 10 | |
| 15.8.0 | 3 / 10 | |
| 15.7.2 | 3 / 9 | |
| 15.7.1 | 2 / 9 | |
| 15.7.0 | 2 / 9 | |
| 15.6.2 | 2 / 9 | |
| 15.6.1 | 3 / 9 | |
| 15.6.0 | 3 / 9 | |
| 15.5.10 | 2 / 9 | |
| 15.5.9 | 2 / 9 | |
| 15.5.8 | 1 / 9 | |
| 15.5.7 | 1 / 9 | |
| 15.5.6 | 1 / 7 | |
| 15.5.5 | 1 / 7 | |
| 15.5.4 | 1 / 7 | |
| 15.5.3 | 1 / 6 | |
| 15.5.2 | 1 / 6 | |
| 15.5.1 | 1 / 3 | |
| 15.5.0 | 1 / 3 | |
| 0.2.0 | 1 / 12 | |
| 0.1.0 | 0 / 11 |
v15.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.7.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: ljharb.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.7.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: ljharb.
v15.7.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: ljharb.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-10. 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 2018-06-19. 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.1
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-02-26. This could indicate a legitimate maintainer transition or an account compromise.
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 was published by a different npm account than previous versions on 2017-09-25. This could indicate a legitimate maintainer transition or an account compromise.
v15.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.7
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 2017-04-11. This could indicate a legitimate maintainer transition or an account compromise.
v15.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.5
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 2017-04-09. This could indicate a legitimate maintainer transition or an account compromise.
v15.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.1
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-04-07. This could indicate a legitimate maintainer transition or an account compromise.
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-04-06. This could indicate a legitimate maintainer transition or an account compromise.