← Home

@logto/create

31
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

simeng_ligaosun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Thin CLI wrapper in the official @logto org; missing metadata is expected for this package type. ai
npm-metadata no-description AI (npm-metadata): Intentional minimal metadata for a CLI shim package in the official Logto monorepo. ai
phantom-deps phantom-dep:@logto/cli AI (phantom-deps): Package is a shell-script wrapper (index.sh) that invokes @logto/cli; no JS import expected. ai

Versions (showing 31 of 31)

Version Deps Published
1.41.0 1 / 0
1.40.1 1 / 0
1.40.0 1 / 0
1.39.0 1 / 0
1.38.0 1 / 0
1.37.1 1 / 0
1.37.0 1 / 0
1.36.0 1 / 0
1.35.0 1 / 0
1.34.0 1 / 0
1.33.0 1 / 0
1.32.0 1 / 0
1.31.0 1 / 0
1.30.1 1 / 0
1.30.0 1 / 0
1.29.0 1 / 0
1.28.0 1 / 0
1.27.0 1 / 0
1.26.0 1 / 0
1.25.0 1 / 0
1.24.1 1 / 0
1.24.0 1 / 0
1.23.1 1 / 0
1.23.0 1 / 0
1.22.0 1 / 0
1.21.0 1 / 0
1.20.0 1 / 0
1.19.0 1 / 0
1.18.0 1 / 0
1.17.0 1 / 0
1.16.0 1 / 0

v1.41.0

1 finding
LOW No provenance attestation provenance

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

v1.27.0

1 finding
LOW No provenance attestation provenance

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

v1.26.0

1 finding
LOW No provenance attestation provenance

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

v1.25.0

1 finding
LOW No provenance attestation provenance

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

v1.24.1

1 finding
LOW No provenance attestation provenance

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

v1.24.0

1 finding
LOW No provenance attestation provenance

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

v1.23.1

1 finding
LOW No provenance attestation provenance

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

v1.23.0

1 finding
LOW No provenance attestation provenance

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

v1.22.0

1 finding
LOW No provenance attestation provenance

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

v1.21.0

1 finding
LOW No provenance attestation provenance

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

v1.20.0

1 finding
LOW No provenance attestation provenance

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

v1.19.0

1 finding
LOW No provenance attestation provenance

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

v1.18.0

1 finding
LOW No provenance attestation provenance

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

v1.17.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.16.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.