@stamhoofd/backend-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:base64-decode | AI (semgrep): Base64 used to decode HMAC secret key — standard crypto pattern, not payload obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo utility package; missing metadata is expected for this package style. | ai |
Versions (showing 100 of 258)
| Version | Deps | Published |
|---|---|---|
| 2.90.3 | 0 / 0 | |
| 2.90.2 | 0 / 0 | |
| 2.90.1 | 0 / 0 | |
| 2.90.0 | 0 / 0 | |
| 2.89.2 | 0 / 0 | |
| 2.89.1 | 0 / 0 | |
| 2.89.0 | 0 / 0 | |
| 2.88.1 | 0 / 0 | |
| 2.88.0 | 0 / 0 | |
| 2.87.1 | 0 / 0 | |
| 2.87.0 | 0 / 0 | |
| 2.86.0 | 0 / 0 | |
| 2.85.4 | 0 / 0 | |
| 2.85.3 | 0 / 0 | |
| 2.85.2 | 0 / 0 | |
| 2.85.1 | 0 / 0 | |
| 2.85.0 | 0 / 0 | |
| 2.84.2 | 0 / 0 | |
| 2.84.1 | 0 / 0 | |
| 2.84.0 | 0 / 0 | |
| 2.83.5 | 0 / 0 | |
| 2.83.4 | 0 / 0 | |
| 2.83.3 | 0 / 0 | |
| 2.83.2 | 0 / 0 | |
| 2.83.1 | 0 / 0 | |
| 2.83.0 | 0 / 0 | |
| 2.82.0 | 0 / 0 | |
| 2.81.0 | 0 / 0 | |
| 2.80.1 | 0 / 0 | |
| 2.80.0 | 0 / 0 | |
| 2.79.8 | 0 / 0 | |
| 2.79.7 | 0 / 0 | |
| 2.79.6 | 0 / 0 | |
| 2.79.5 | 0 / 0 | |
| 2.79.4 | 0 / 0 | |
| 2.79.3 | 0 / 0 | |
| 2.79.2 | 0 / 0 | |
| 2.79.1 | 0 / 0 | |
| 2.79.0 | 0 / 0 | |
| 2.78.4 | 0 / 0 | |
| 2.78.3 | 0 / 0 | |
| 2.78.2 | 0 / 0 | |
| 2.78.1 | 0 / 0 | |
| 2.78.0 | 0 / 0 | |
| 2.77.5 | 0 / 0 | |
| 2.77.4 | 0 / 0 | |
| 2.77.3 | 0 / 0 | |
| 2.77.2 | 0 / 0 | |
| 2.77.1 | 0 / 0 | |
| 2.77.0 | 0 / 0 | |
| 2.76.0 | 0 / 0 | |
| 2.75.2 | 0 / 0 | |
| 2.75.1 | 0 / 0 | |
| 2.75.0 | 0 / 0 | |
| 2.74.0 | 0 / 0 | |
| 2.73.3 | 0 / 0 | |
| 2.73.2 | 0 / 0 | |
| 2.73.1 | 0 / 0 | |
| 2.73.0 | 0 / 0 | |
| 2.72.0 | 0 / 0 | |
| 2.71.0 | 0 / 0 | |
| 2.70.0 | 0 / 0 | |
| 2.69.0 | 0 / 0 | |
| 2.68.0 | 0 / 0 | |
| 2.67.0 | 0 / 0 | |
| 2.66.0 | 0 / 0 | |
| 2.65.2 | 0 / 0 | |
| 2.65.1 | 0 / 0 | |
| 2.65.0 | 0 / 0 | |
| 2.64.0 | 0 / 0 | |
| 2.63.0 | 0 / 0 | |
| 2.62.0 | 0 / 0 | |
| 2.61.1 | 0 / 0 | |
| 2.61.0 | 0 / 0 | |
| 2.60.0 | 0 / 0 | |
| 2.59.0 | 0 / 0 | |
| 2.58.0 | 0 / 0 | |
| 2.57.1 | 0 / 0 | |
| 2.57.0 | 0 / 0 | |
| 2.56.0 | 0 / 0 | |
| 2.55.2 | 0 / 0 | |
| 2.55.1 | 0 / 0 | |
| 2.55.0 | 0 / 0 | |
| 2.54.2 | 0 / 0 | |
| 2.54.1 | 0 / 0 | |
| 2.54.0 | 0 / 0 | |
| 2.53.0 | 0 / 0 | |
| 2.52.0 | 0 / 0 | |
| 2.51.4 | 0 / 0 | |
| 2.51.3 | 0 / 0 | |
| 2.51.2 | 0 / 0 | |
| 2.51.1 | 0 / 0 | |
| 2.51.0 | 0 / 0 | |
| 2.50.2 | 0 / 0 | |
| 2.50.0 | 0 / 0 | |
| 2.49.1 | 0 / 0 | |
| 2.49.0 | 0 / 0 | |
| 2.48.1 | 0 / 0 | |
| 2.48.0 | 0 / 0 | |
| 2.46.0 | 0 / 0 |
v2.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.75.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.75.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.