micro
Asynchronous HTTP microservices
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): Publisher change from leo to timneutkens occurred in 2019 as part of a documented Zeit/Vercel org transition. timneutkens is a well-known Vercel core contributor with strong track record. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used only to read the project's own package.json to find the entry point — a standard CLI pattern with no arbitrary module loading risk. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 3 / 6 | |
| 10.0.0 | 3 / 6 | |
| 9.4.1 | 3 / 0 | |
| 9.4.0 | 3 / 0 | |
| 9.3.4 | 4 / 13 | |
| 9.3.3 | 5 / 13 | |
| 9.3.2 | 5 / 13 | |
| 9.3.1 | 5 / 13 | |
| 9.3.0 | 5 / 13 | |
| 9.2.0 | 4 / 15 | |
| 9.1.4 | 4 / 13 | |
| 9.1.3 | 4 / 13 | |
| 9.1.2 | 4 / 13 | |
| 9.1.1 | 4 / 13 | |
| 9.1.0 | 4 / 13 | |
| 9.0.2 | 4 / 13 | |
| 9.0.1 | 4 / 13 | |
| 9.0.0 | 4 / 13 | |
| 8.0.4 | 4 / 13 | |
| 8.0.3 | 3 / 13 | |
| 8.0.2 | 3 / 13 | |
| 8.0.1 | 3 / 13 | |
| 8.0.0 | 3 / 13 | |
| 7.3.3 | 14 / 13 | |
| 7.3.2 | 14 / 13 | |
| 7.3.1 | 14 / 13 | |
| 7.3.0 | 14 / 13 | |
| 7.2.2 | 14 / 10 | |
| 7.2.1 | 14 / 10 | |
| 7.2.0 | 14 / 10 | |
| 7.1.0 | 14 / 8 | |
| 7.0.6 | 14 / 8 | |
| 7.0.5 | 14 / 8 | |
| 7.0.4 | 13 / 8 | |
| 7.0.3 | 12 / 8 | |
| 7.0.2 | 12 / 8 | |
| 7.0.1 | 12 / 8 | |
| 7.0.0 | 12 / 7 | |
| 6.2.1 | 6 / 6 | |
| 6.2.0 | 6 / 6 | |
| 6.1.0 | 5 / 6 | |
| 6.0.2 | 5 / 7 | |
| 6.0.1 | 5 / 6 | |
| 5.0.1 | 6 / 14 | |
| 5.0.0 | 11 / 13 | |
| 4.1.1 | 11 / 13 | |
| 4.1.0 | 10 / 13 | |
| 4.0.0 | 10 / 16 | |
| 3.0.0 | 11 / 15 | |
| 2.1.0 | 11 / 15 | |
| 2.0.0 | 10 / 15 |
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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-07-17. This could indicate a legitimate maintainer transition or an account compromise.
v9.3.4
2 findingsThis version was published by a different npm account than previous versions on 2019-05-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.
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.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 2018-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v9.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 2018-04-23. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
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 2018-03-11. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.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 2018-03-10. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.