api-easy
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): qs is a well-known, legitimate query string library appropriate for a REST API testing tool; addition is benign and consistent with package purpose. | ai | |
| provenance | no-provenance | AI (provenance): Mature package (15yr history) with established publisher; provenance absence is not a security risk for this stable release. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher indexzero is a highly trusted, long-standing npm author. Dormancy is consistent with a mature, stable utility package rather than an account takeover. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): [email protected] is a well-known, historically popular HTTP library. Deprecated but not malicious; appropriate for this package's age and use case. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 3 / 3 | |
| 0.3.6 | 4 / 3 | |
| 0.3.5 | 4 / 3 | |
| 0.3.4 | 4 / 3 | |
| 0.3.3 | 3 / 3 | |
| 0.3.2 | 3 / 3 | |
| 0.3.0 | 3 / 3 | |
| 0.2.3 | 2 / 1 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.