@logto/api
Logto API types and clients.
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:hapi | AI (typosquat): @logto/api is a scoped package from the official logto-io org; Levenshtein match to 'hapi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package from logto-io org; no relation to 'pg'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package from logto-io org; no relation to 'joi'. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package from logto-io org; no relation to 'ajv'. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.40.0 | 1 / 9 | |
| 1.39.0 | 1 / 9 | |
| 1.38.0 | 1 / 9 | |
| 1.37.1 | 1 / 9 | |
| 1.37.0 | 1 / 9 | |
| 1.36.0 | 1 / 9 | |
| 1.35.0 | 1 / 8 | |
| 1.34.0 | 1 / 8 | |
| 1.33.0 | 1 / 8 | |
| 1.32.0 | 1 / 8 | |
| 1.31.0 | 1 / 8 | |
| 1.30.1 | 1 / 8 | |
| 1.30.0 | 1 / 8 |
v1.40.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (simeng_li) than the most recent previously approved version (gaosun) on 2026-05-29, but simeng_li is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.39.0
2 findingsPackage name '@logto/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.