@sigmance/razor
<p align="center"> <img src="./.github/razor-logo.png" alt="Razor logo" width="220" /> </p>
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): CLI tool spreads process.env to pass env to child process with updated PATH — standard pattern, not a secret leak. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.125.9 | 0 / 0 | |
| 0.125.8 | 0 / 0 | |
| 0.125.7 | 0 / 0 | |
| 0.125.4 | 0 / 0 | |
| 0.125.3 | 0 / 0 | |
| 0.125.2 | 0 / 0 | |
| 0.125.1 | 0 / 0 | |
| 0.117.18 | 0 / 0 | |
| 0.117.17 | 0 / 0 | |
| 0.117.16 | 0 / 0 | |
| 0.117.15 | 0 / 0 |
v0.125.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.117.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.117.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.117.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.117.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.