proper-lockfile
A inter-process and inter-machine lockfile utility that works on a local or network file system
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from satazor to hugomrdias within the same moxystudio org; hugomrdias is a well-established publisher with 248 approved packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable utility; long gaps between releases are normal. Publisher is legitimate within the moxystudio org. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 3 / 16 | |
| 4.1.1 | 3 / 16 | |
| 4.1.0 | 3 / 16 | |
| 4.0.0 | 3 / 16 | |
| 3.2.0 | 3 / 15 | |
| 3.1.0 | 3 / 15 | |
| 3.0.2 | 2 / 15 | |
| 3.0.1 | 2 / 15 | |
| 3.0.0 | 2 / 14 | |
| 2.0.1 | 2 / 11 | |
| 2.0.0 | 2 / 11 | |
| 1.2.0 | 4 / 11 | |
| 1.1.3 | 4 / 8 | |
| 1.1.2 | 4 / 8 | |
| 1.1.1 | 4 / 7 | |
| 1.1.0 | 4 / 7 | |
| 1.0.2 | 4 / 7 | |
| 1.0.1 | 4 / 7 | |
| 1.0.0 | 4 / 7 | |
| 0.6.1 | 4 / 7 | |
| 0.6.0 | 4 / 7 | |
| 0.5.0 | 4 / 7 | |
| 0.4.0 | 6 / 6 | |
| 0.3.1 | 6 / 6 | |
| 0.3.0 | 6 / 6 | |
| 0.2.1 | 4 / 6 | |
| 0.2.0 | 4 / 6 | |
| 0.1.5 | 4 / 6 | |
| 0.1.4 | 4 / 6 | |
| 0.1.3 | 4 / 6 | |
| 0.1.2 | 4 / 6 | |
| 0.1.1 | 4 / 6 | |
| 0.1.0 | 4 / 6 |
v4.1.2
2 findingsThis version was published by a different npm account than previous versions on 2021-01-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-18. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.