← Home

@logto/cli

npm Repository Homepage

Logto CLI.

9
Versions
MPL-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

simeng_ligaosun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Publisher is a known maintainer on prior approved versions; no material code changes from last approved version. ai
dependencies unvetted-dep:@silverhand/slonik AI (dependencies): Internal Silverhand fork of slonik; stable dependency across Logto CLI versions. ai
dependencies unvetted-dep:@logto/connector-kit AI (dependencies): First-party Logto package; stable dependency across Logto CLI versions. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @logto/cli is a scoped package from the official Logto org; Levenshtein match to 'joi' is a false positive. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding used for OIDC private key handling — legitimate cryptographic use, not obfuscation. ai
phantom-deps phantom-dep:nanoid AI (phantom-deps): nanoid is listed in package.json dependencies; phantom-dep heuristic false positive. ai

Versions (showing 9 of 9)

Version Deps Published
1.40.0 21 / 16
1.39.0 21 / 16
1.37.1 21 / 16
1.37.0 21 / 16
1.34.0 21 / 16
1.33.0 21 / 16
1.30.0 21 / 16
1.29.0 21 / 16
1.28.0 21 / 16

v1.40.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gaosun → simeng_li (on 2026-05-29, known maintainer) provenance

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

v1.37.1

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.

v1.37.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.

v1.34.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.

v1.33.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.

v1.30.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.

v1.29.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.

v1.28.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.