@stamhoofd/models
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency monorepo CI releases; pattern is stable across 229 versions from this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private monorepo package; missing description/repo/keywords is expected for internal @stamhoofd packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; no description is consistent across all @stamhoofd packages. | ai | |
| phantom-deps | phantom-dep:@simonbackx/simple-endpoints | AI (phantom-deps): Monorepo package; referenced in config/type declarations rather than direct imports is expected. | ai |
Versions (showing 44 of 244)
| Version | Deps | Published |
|---|---|---|
| 2.32.3 | 2 / 1 | |
| 2.32.2 | 2 / 1 | |
| 2.32.1 | 2 / 1 | |
| 2.32.0 | 2 / 1 | |
| 2.31.0 | 2 / 1 | |
| 2.30.6 | 2 / 1 | |
| 2.30.5 | 2 / 1 | |
| 2.30.4 | 2 / 1 | |
| 2.30.3 | 2 / 1 | |
| 2.30.2 | 2 / 1 | |
| 2.30.1 | 2 / 1 | |
| 2.30.0 | 2 / 1 | |
| 2.29.0 | 2 / 1 | |
| 2.28.0 | 2 / 1 | |
| 2.27.2 | 2 / 1 | |
| 2.26.0 | 2 / 1 | |
| 2.25.2 | 2 / 1 | |
| 2.25.0 | 2 / 1 | |
| 2.24.0 | 2 / 1 | |
| 2.23.0 | 2 / 1 | |
| 2.22.0 | 2 / 1 | |
| 2.21.2 | 2 / 1 | |
| 2.21.1 | 2 / 1 | |
| 2.21.0 | 2 / 1 | |
| 2.20.0 | 2 / 1 | |
| 2.19.0 | 2 / 1 | |
| 2.18.0 | 2 / 1 | |
| 2.17.3 | 2 / 1 | |
| 2.17.0 | 2 / 1 | |
| 2.16.0 | 2 / 1 | |
| 2.13.0 | 2 / 1 | |
| 2.12.0 | 2 / 1 | |
| 2.11.0 | 2 / 1 | |
| 2.10.2 | 2 / 1 | |
| 2.9.0 | 2 / 1 | |
| 2.8.0 | 2 / 1 | |
| 2.7.0 | 2 / 1 | |
| 2.6.0 | 2 / 1 | |
| 2.5.0 | 2 / 1 | |
| 2.4.0 | 2 / 1 | |
| 2.3.0 | 2 / 1 | |
| 2.2.0 | 2 / 1 | |
| 2.1.3 | 2 / 1 | |
| 2.1.1 | 2 / 1 |
v2.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.