← Home

loro-prosemirror

npm Repository Homepage
20
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

rem2018

Keywords

rich-textprosemirrorlorolocal-firstcrdt

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA Sigstore attestation; legitimate CI/CD migration. ai
provenance missing-githead AI (provenance): Missing gitHead is expected when publishing via GitHub Actions CI without explicit gitHead injection; SLSA attestation compensates. ai

Versions (showing 20 of 20)

Version Deps Published
0.4.3 4 / 11
0.4.2 1 / 17
0.4.1 1 / 17
0.4.0 1 / 17
0.3.7 1 / 17
0.3.6 1 / 17
0.3.5 1 / 17
0.3.1 1 / 17
0.3.0 1 / 17
0.2.3 1 / 17
0.2.2 1 / 17
0.2.1 1 / 16
0.2.0 1 / 16
0.1.0 1 / 16
0.0.7 1 / 16
0.0.6 1 / 16
0.0.4 1 / 16
0.0.3 2 / 15
0.0.2 2 / 15
0.0.1 2 / 11

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rem2018.

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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