@stamhoofd/backend-renderer
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing README/keywords/repo metadata is expected for private backend packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo internal package; no description is consistent across all @stamhoofd packages. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Monorepo build; deps may be used transitively or in config files not directly scanned. | ai | |
| phantom-deps | phantom-dep:mysql2 | AI (phantom-deps): Monorepo build; deps may be used transitively or in config files not directly scanned. | ai | |
| phantom-deps | phantom-dep:mockdate | AI (phantom-deps): Monorepo build; deps may be used transitively or in config files not directly scanned. | ai | |
| phantom-deps | phantom-dep:@simonbackx/simple-logging | AI (phantom-deps): Monorepo build; deps may be used transitively or in config files not directly scanned. | ai |
Versions (showing 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 2.121.0 | 7 / 4 | |
| 2.120.6 | 7 / 4 | |
| 2.120.5 | 7 / 4 | |
| 2.120.4 | 7 / 4 | |
| 2.120.3 | 7 / 4 | |
| 2.120.2 | 7 / 4 | |
| 2.120.1 | 7 / 4 | |
| 2.120.0 | 7 / 4 | |
| 2.119.0 | 7 / 4 | |
| 2.118.1 | 7 / 4 | |
| 2.118.0 | 7 / 4 | |
| 2.117.1 | 7 / 4 | |
| 2.117.0 | 7 / 4 | |
| 2.116.0 | 7 / 4 | |
| 2.115.1 | 7 / 4 | |
| 2.115.0 | 7 / 4 | |
| 2.114.1 | 7 / 4 | |
| 2.114.0 | 7 / 4 | |
| 2.113.0 | 7 / 4 | |
| 2.112.0 | 7 / 4 | |
| 2.111.0 | 7 / 4 | |
| 2.110.0 | 7 / 4 | |
| 2.109.0 | 7 / 4 | |
| 2.108.0 | 7 / 4 | |
| 2.107.3 | 7 / 4 | |
| 2.107.2 | 7 / 4 | |
| 2.107.1 | 7 / 4 | |
| 2.107.0 | 7 / 4 | |
| 2.106.1 | 7 / 4 | |
| 2.106.0 | 7 / 4 | |
| 2.105.0 | 7 / 4 | |
| 2.104.0 | 7 / 4 | |
| 2.103.1 | 7 / 4 | |
| 2.103.0 | 7 / 4 | |
| 2.102.0 | 7 / 4 | |
| 2.101.0 | 7 / 4 | |
| 2.100.1 | 7 / 4 | |
| 2.100.0 | 7 / 4 | |
| 2.99.1 | 7 / 4 | |
| 2.99.0 | 7 / 4 | |
| 2.98.0 | 7 / 4 | |
| 2.97.3 | 7 / 4 | |
| 2.97.2 | 7 / 4 | |
| 2.97.1 | 7 / 4 | |
| 2.97.0 | 7 / 4 | |
| 2.96.3 | 7 / 4 | |
| 2.96.2 | 7 / 4 | |
| 2.96.1 | 7 / 4 | |
| 2.96.0 | 7 / 4 | |
| 2.95.3 | 7 / 4 | |
| 2.95.2 | 7 / 4 | |
| 2.95.1 | 7 / 4 | |
| 2.95.0 | 7 / 4 | |
| 2.94.0 | 7 / 4 | |
| 2.93.0 | 7 / 4 | |
| 2.92.0 | 7 / 4 | |
| 2.91.0 | 7 / 4 | |
| 2.90.3 | 7 / 4 | |
| 2.90.2 | 7 / 4 | |
| 2.90.1 | 7 / 4 | |
| 2.90.0 | 7 / 4 | |
| 2.89.2 | 7 / 4 | |
| 2.89.1 | 7 / 4 | |
| 2.89.0 | 7 / 4 | |
| 2.88.1 | 7 / 4 | |
| 2.88.0 | 7 / 4 | |
| 2.87.1 | 7 / 4 | |
| 2.87.0 | 7 / 4 | |
| 2.86.0 | 7 / 4 | |
| 2.85.4 | 7 / 4 | |
| 2.85.3 | 7 / 4 | |
| 2.85.2 | 7 / 4 | |
| 2.85.1 | 7 / 4 | |
| 2.85.0 | 7 / 4 | |
| 2.84.2 | 7 / 4 | |
| 2.84.1 | 7 / 4 | |
| 2.84.0 | 7 / 4 | |
| 2.83.5 | 7 / 4 | |
| 2.83.4 | 7 / 4 | |
| 2.83.3 | 7 / 4 | |
| 2.83.2 | 7 / 4 | |
| 2.83.1 | 7 / 4 | |
| 2.83.0 | 7 / 4 |
v2.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.119.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.118.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.118.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.117.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.117.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.116.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.115.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.115.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.114.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.113.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.111.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.109.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.108.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.103.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.99.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.84.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.84.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.