@logto/schemas
The central packages for all database schemas and their TypeScript definitions and utilities.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Logto org package; inactivity gap consistent with project release cadence, not account takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance absence is common and not a security concern for this mature, ecosystem-trusted package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Schema package regularly adds new table/model files across versions; pattern is consistent with normal growth. | ai | |
| dependencies | unvetted-dep:@withtyped/server | AI (dependencies): Part of the same Silverhand/logto ecosystem; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@logto/language-kit | AI (dependencies): Internal @logto org package; stable sibling dependency. | ai | |
| dependencies | unvetted-dep:@logto/connector-kit | AI (dependencies): Internal @logto org package; stable sibling dependency. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.40.1 | 8 / 17 | |
| 1.39.0 | 8 / 17 | |
| 1.38.0 | 8 / 17 | |
| 1.37.1 | 8 / 17 | |
| 1.36.0 | 8 / 17 | |
| 1.34.0 | 8 / 17 | |
| 1.30.1 | 8 / 17 |
v1.40.1
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
1 findingPackage 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.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.