airbnb-prop-types
Custom React PropType validators that we use at Airbnb.
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): Legitimate transfer from airbnb org to ljharb (Jordan Harband), who is the listed author and a highly trusted npm maintainer. | ai | |
| phantom-deps | phantom-dep:has | AI (phantom-deps): `has` is declared in dependencies and used at runtime; phantom-dep detection is a false positive. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Airbnb engineers added to the org; consistent with legitimate team management by the trusted publisher ljharb. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of the generic 'airbnb' org account in favor of individual engineers is a known Airbnb npm org management pattern, not a takeover signal. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in build-test/index.js, a test infrastructure helper for loading test modules. Not in runtime code; stable false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.16.0 | 9 / 24 | |
| 2.15.0 | 10 / 24 | |
| 2.14.0 | 10 / 24 | |
| 2.13.2 | 10 / 24 | |
| 2.13.1 | 10 / 24 | |
| 2.13.0 | 10 / 24 | |
| 2.12.0 | 10 / 24 | |
| 2.11.0 | 9 / 22 | |
| 2.10.0 | 9 / 22 | |
| 2.9.0 | 9 / 21 | |
| 2.8.1 | 8 / 19 | |
| 2.8.0 | 8 / 18 | |
| 2.7.1 | 8 / 18 | |
| 2.7.0 | 7 / 18 | |
| 2.6.1 | 6 / 17 | |
| 2.6.0 | 6 / 17 | |
| 2.5.4 | 6 / 16 | |
| 2.5.3 | 6 / 16 | |
| 2.5.2 | 5 / 16 | |
| 2.5.1 | 2 / 16 | |
| 2.5.0 | 2 / 16 | |
| 2.4.1 | 1 / 16 | |
| 2.4.0 | 1 / 16 | |
| 2.3.0 | 1 / 15 | |
| 2.2.0 | 1 / 15 | |
| 2.1.1 | 1 / 15 | |
| 2.1.0 | 1 / 15 | |
| 2.0.1 | 1 / 15 | |
| 2.0.0 | 1 / 15 | |
| 1.3.2 | 2 / 13 | |
| 1.3.1 | 2 / 13 | |
| 1.3.0 | 2 / 13 | |
| 1.2.0 | 1 / 13 | |
| 1.1.1 | 1 / 13 | |
| 1.1.0 | 1 / 13 |
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
2 findingsThis version was published by a different npm account than previous versions on 2019-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.
v2.13.0
2 findingsThis version was published by a different npm account than previous versions on 2019-04-04. 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.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.