← Home

api

1
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

gkobergerdomharringtonmjcuvakanadguptajonursenbachrafegoldbergiliastdannobytesgratcliffllimllibdarrenyongazinder1kellyjosephpriceowlbert

Keywords

apiopenapisdkswagger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): 'api' is a 14-year-old generic package name by ReadMe.io, not a typosquat of 'hapi'. Levenshtein distance on short names produces false positives here. ai
typosquat typosquat.levenshtein:pg AI (typosquat): 'api' is a well-established generic package name; not a typosquat of 'pg'. Short-name Levenshtein false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): 'api' is a well-established generic package name; not a typosquat of 'joi'. Short-name Levenshtein false positive. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): 'api' is a well-established generic package name; not a typosquat of 'ajv'. Short-name Levenshtein false positive. ai

Versions (showing 1 of 1)

Version Deps Published
6.1.3 28 / 17

v6.1.3

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name 'api' is 1 edit(s) away from popular package 'hapi'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.