@anywaydata/api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @anywaydata/api; 'api' substring match to 'pg' is a false positive, no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @anywaydata/api; Levenshtein match to 'joi' is a false positive on the short 'api' suffix. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @anywaydata/api; Levenshtein match to 'ajv' is a false positive on the short 'api' suffix. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): The scoped name @anywaydata/api is not a plausible typosquat of hapi; Levenshtein match is coincidental on the 'api' suffix. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP 127.0.0.1 appears only in test helper code for localhost; not a real exfiltration indicator. | ai |
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.