@ls-stack/pkg-manager
CLI tool for managing package publishing with hash-based change tracking and monorepo support
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ls-stack/cli | AI (dependencies): @ls-stack/cli is a sibling package from the same author/org (lucasols/@ls-stack namespace), consistent with this package's stated purpose as an internal CLI tool. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of packages); no other risk signals elevate this to a concern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.4 | 3 / 6 | |
| 0.7.3 | 3 / 6 | |
| 0.7.2 | 3 / 6 | |
| 0.7.1 | 3 / 6 | |
| 0.7.0 | 3 / 6 | |
| 0.6.0 | 3 / 6 | |
| 0.5.1 | 3 / 6 | |
| 0.5.0 | 3 / 6 | |
| 0.4.0 | 3 / 6 | |
| 0.3.0 | 3 / 6 | |
| 0.2.2 | 2 / 6 | |
| 0.2.1 | 2 / 6 | |
| 0.2.0 | 2 / 5 |
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.