← Home

@logto/core-kit

npm Repository Homepage
13
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
semgrep semgrep:toplevel-fetch AI (semgrep): Fetch targets api.pwnedpasswords.com for HIBP password breach checking — documented, benign use case stable across versions. ai
phantom-deps phantom-dep:@logto/language-kit AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep heuristic false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
2.11.0 4 / 15
2.10.0 4 / 15
2.9.0 4 / 15
2.8.0 4 / 15
2.7.1 4 / 15
2.7.0 4 / 15
2.6.1 4 / 15
2.6.0 4 / 15
2.5.4 4 / 15
2.5.3 4 / 15
2.5.2 4 / 15
2.5.1 4 / 15
2.5.0 5 / 15

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.4

1 finding
LOW No provenance attestation provenance

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

v2.5.3

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

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