← Home

@pkcprotocol/proper-lock-file

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rinse12

Keywords

locklockingfilelockfilefscross-process

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from human account to GitHub Actions is expected for CI/CD-published packages with SLSA provenance attestation. ai

Versions (showing 3 of 3)

Version Deps Published
4.2.1 3 / 20
4.2.0 3 / 20
4.1.2 3 / 13

v4.2.0

2 findings
HIGH Publisher changed: rinse12 → GitHub Actions (on 2026-04-17) provenance

This version was published by a different npm account than previous versions on 2026-04-17. This could indicate a legitimate maintainer transition or an account compromise.

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

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.