← Home

@netlify/api

npm Repository Homepage
17
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

seanrobertsbiilmanneduardoboucasnetlify-botsarahettermikewenkathmbeckhrishikeshkvitaliyrberdavyouvalvserhalp-netlifydomitriusanthonyakardettbarnseancdavismlgualtieri-gatsby

Keywords

api clientjs clientnetlifynode client

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:picoquery AI (dependencies): Legitimate query-string utility; stable dependency of this package across versions. ai
dependencies unvetted-dep:@netlify/open-api AI (dependencies): First-party Netlify package; stable dependency of this package across versions. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @netlify/api cannot typosquat 'hapi'; Levenshtein match is a false positive for scoped packages. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @netlify/api cannot typosquat 'pg'; false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @netlify/api cannot typosquat 'joi'; false positive. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @netlify/api cannot typosquat 'ajv'; false positive. ai

Versions (showing 17 of 17)

Version Deps Published
14.0.19 4 / 6
14.0.18 4 / 7
14.0.17 4 / 7
14.0.16 4 / 7
14.0.15 4 / 7
14.0.14 4 / 7
14.0.13 4 / 7
14.0.12 4 / 7
14.0.11 4 / 7
14.0.10 4 / 7
14.0.9 4 / 7
14.0.8 4 / 7
14.0.7 4 / 7
14.0.6 4 / 7
14.0.5 4 / 7
14.0.4 4 / 7
14.0.0 6 / 9

v14.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.18

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

Package name '@netlify/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.

v14.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.13

1 finding
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.

v14.0.12

1 finding
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.

v14.0.11

1 finding
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.

v14.0.10

1 finding
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.

v14.0.9

1 finding
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.

v14.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.6

1 finding
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.

v14.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.4

1 finding
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.

v14.0.0

1 finding
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.