@laserfiche/lf-js-utils
7
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
lfitslf-ke-jinpaolo.laserfichebzajzon-laserfichealexgomezlf
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher with SLSA provenance attestation; consistent with org-level automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA attestation; no malicious indicators present. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.0.15 | 0 / 9 | |
| 4.0.14 | 0 / 9 | |
| 4.0.13 | 0 / 13 | |
| 4.0.12 | 0 / 13 | |
| 4.0.11 | 0 / 13 | |
| 4.0.10 | 0 / 13 | |
| 4.0.9 | 0 / 13 |
v4.0.15
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.12
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
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.
v4.0.9
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.