@rcompat/env
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Package's explicit purpose is env-var management; spreading process.env is intentional and expected behavior. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @rcompat/env is not a plausible typosquat of ajv; different namespace, purpose, and edit distance is coincidental. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 1 / 1 | |
| 0.22.2 | 1 / 1 | |
| 0.22.1 | 1 / 1 | |
| 0.22.0 | 1 / 1 | |
| 0.21.0 | 1 / 1 | |
| 0.20.1 | 1 / 1 | |
| 0.20.0 | 1 / 1 | |
| 0.19.0 | 1 / 1 | |
| 0.18.0 | 1 / 1 | |
| 0.17.2 | 1 / 1 | |
| 0.17.1 | 1 / 1 | |
| 0.17.0 | 1 / 1 | |
| 0.16.0 | 1 / 1 | |
| 0.15.1 | 1 / 1 | |
| 0.15.0 | 1 / 1 | |
| 0.14.0 | 2 / 0 | |
| 0.13.0 | 2 / 0 | |
| 0.12.0 | 2 / 0 | |
| 0.11.0 | 2 / 0 | |
| 0.10.0 | 2 / 0 | |
| 0.9.2 | 3 / 0 | |
| 0.9.1 | 4 / 0 | |
| 0.9.0 | 4 / 0 | |
| 0.8.0 | 4 / 0 | |
| 0.7.1 | 4 / 0 | |
| 0.7.0 | 4 / 0 |
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage 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.