@push.rocks/qenv
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes user-supplied env var payloads; not obfuscation — stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartpath | AI (phantom-deps): Same-org dep declared but may be used transitively; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.1.4 | 5 / 4 | |
| 6.1.1 | 5 / 4 | |
| 6.1.0 | 5 / 5 | |
| 6.0.8 | 5 / 5 | |
| 6.0.7 | 5 / 5 | |
| 6.0.6 | 5 / 5 |
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.