airbnb-js-shims
JS language shims used by 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): lencioni is a well-established npm publisher (452 approved packages) within the Airbnb ecosystem; the transition from ljharb to lencioni is a legitimate maintainer handoff for this Airbnb org package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (airbnbeng, milesj, schleyfox) are consistent with Airbnb internal team reorganization for this official Airbnb org package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of 'airbnb' account alongside addition of airbnbeng and other Airbnb team members reflects an org-level account restructuring, not a hostile takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Shims/polyfills packages are inherently low-churn; 203-day dormancy is expected for a stable utility package. No malicious indicators accompany the resumed activity. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 17 / 5 | |
| 2.2.0 | 17 / 5 | |
| 2.1.1 | 15 / 6 | |
| 2.1.0 | 15 / 6 | |
| 2.0.0 | 14 / 6 | |
| 1.7.1 | 16 / 6 | |
| 1.7.0 | 16 / 6 | |
| 1.6.0 | 15 / 6 | |
| 1.5.2 | 14 / 6 | |
| 1.5.1 | 14 / 6 | |
| 1.5.0 | 14 / 6 | |
| 1.4.1 | 12 / 5 | |
| 1.4.0 | 12 / 5 | |
| 1.3.0 | 10 / 5 | |
| 1.2.0 | 9 / 5 | |
| 1.1.1 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.1 | 8 / 6 | |
| 1.0.0 | 8 / 1 |
v2.2.1
2 findingsThis version was published by a different npm account than previous versions on 2019-11-15. 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.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
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
2 findingsPackage 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-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsPackage 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-02-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.1
2 findingsPackage 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 2016-08-18. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.