light-my-request
Fake HTTP injection library
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): matteo.collina is a core Fastify maintainer and highly trusted npm publisher; the transition from eomm is a routine org-level change within the Fastify ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fdawgs and metcoder95 are known Fastify ecosystem contributors; fdawgs is even listed in package.json contributors. Addition is a legitimate org governance change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): rafaelgss stepping back from this package is consistent with known Fastify org maintainer rotation; no takeover indicators present. | ai |
Versions (showing 77 of 77)
| Version | Deps | Published |
|---|---|---|
| 6.6.0 | 3 / 15 | |
| 6.5.1 | 3 / 14 | |
| 6.5.0 | 3 / 14 | |
| 6.4.0 | 3 / 14 | |
| 6.3.0 | 3 / 13 | |
| 6.2.0 | 3 / 13 | |
| 6.1.0 | 3 / 13 | |
| 6.0.0 | 3 / 13 | |
| 5.14.0 | 3 / 13 | |
| 5.13.0 | 3 / 13 | |
| 5.12.0 | 3 / 11 | |
| 5.11.1 | 3 / 11 | |
| 5.11.0 | 3 / 12 | |
| 5.10.0 | 3 / 12 | |
| 5.9.2 | 3 / 12 | |
| 5.9.1 | 3 / 12 | |
| 5.9.0 | 3 / 12 | |
| 5.8.0 | 3 / 12 | |
| 5.7.0 | 3 / 12 | |
| 5.6.1 | 3 / 12 | |
| 5.6.0 | 3 / 12 | |
| 5.5.1 | 3 / 12 | |
| 5.5.0 | 3 / 12 | |
| 5.4.0 | 3 / 12 | |
| 5.3.0 | 3 / 12 | |
| 5.2.0 | 3 / 12 | |
| 5.1.0 | 3 / 12 | |
| 5.0.0 | 4 / 11 | |
| 4.12.0 | 4 / 11 | |
| 4.11.0 | 3 / 12 | |
| 4.10.1 | 4 / 11 | |
| 4.10.0 | 4 / 11 | |
| 4.9.0 | 4 / 11 | |
| 4.8.0 | 4 / 11 | |
| 4.7.1 | 4 / 11 | |
| 4.7.0 | 4 / 11 | |
| 4.6.0 | 4 / 11 | |
| 4.5.0 | 5 / 11 | |
| 4.4.4 | 5 / 11 | |
| 4.4.3 | 5 / 11 | |
| 4.4.2 | 5 / 9 | |
| 4.4.1 | 5 / 8 | |
| 4.4.0 | 4 / 9 | |
| 4.3.0 | 5 / 8 | |
| 4.2.1 | 5 / 8 | |
| 4.2.0 | 5 / 8 | |
| 4.1.1 | 5 / 7 | |
| 4.1.0 | 5 / 7 | |
| 4.0.2 | 4 / 7 | |
| 4.0.1 | 4 / 7 | |
| 4.0.0 | 4 / 7 | |
| 3.8.0 | 4 / 7 | |
| 3.7.4 | 4 / 6 | |
| 3.7.3 | 4 / 6 | |
| 3.7.2 | 4 / 6 | |
| 3.7.1 | 4 / 6 | |
| 3.7.0 | 4 / 6 | |
| 3.6.3 | 2 / 6 | |
| 3.6.2 | 2 / 6 | |
| 3.6.1 | 2 / 6 | |
| 3.6.0 | 2 / 6 | |
| 3.5.0 | 2 / 6 | |
| 3.4.1 | 2 / 6 | |
| 3.4.0 | 2 / 6 | |
| 3.3.0 | 2 / 6 | |
| 3.2.0 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.0 | 2 / 4 | |
| 2.0.3 | 3 / 4 | |
| 2.0.2 | 3 / 3 | |
| 2.0.1 | 3 / 3 | |
| 2.0.0 | 3 / 3 | |
| 1.1.2 | 2 / 3 | |
| 1.1.1 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.0 | 1 / 2 | |
| 0.0.1 | 0 / 0 |
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsThis version was published by a different npm account than previous versions on 2025-01-08. 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.
v6.4.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-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.
v6.3.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-27. 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.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-09-02. 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.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.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 2024-04-11. This could indicate a legitimate maintainer transition or an account compromise.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.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 2024-02-23. This could indicate a legitimate maintainer transition or an account compromise.
v5.11.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 2023-09-12. This could indicate a legitimate maintainer transition or an account compromise.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.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 2022-09-09. This could indicate a legitimate maintainer transition or an account compromise.
v5.5.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 2022-08-22. This could indicate a legitimate maintainer transition or an account compromise.
v5.5.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 2022-08-17. This could indicate a legitimate maintainer transition or an account compromise.
v5.4.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 2022-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.