@mrsf/cli
CLI and library for the Markdown Review Sidecar Format (MRSF)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @mrsf/cli is a scoped CLI package unrelated to joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is listed as a runtime dependency in package.json; may be used indirectly or in config generation. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 9 / 6 | |
| 0.4.1 | 9 / 6 | |
| 0.4.0 | 9 / 6 | |
| 0.3.1 | 9 / 6 | |
| 0.3.0 | 9 / 5 | |
| 0.2.3 | 9 / 5 | |
| 0.2.2 | 8 / 5 | |
| 0.2.1 | 8 / 5 | |
| 0.2.0 | 8 / 5 | |
| 0.1.0 | 7 / 5 |
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.