@stamhoofd/backend
To run, make sure you set your environment variables.
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): Monorepo with coordinated version bumps across many @stamhoofd/* packages; rapid publish is expected behavior. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are well-known libraries or sibling monorepo packages at matching version; consistent with coordinated monorepo release pattern. | ai | |
| phantom-deps | phantom-dep:mysql2 | AI (phantom-deps): mysql2 is a declared runtime dep; loaded via config/convention in this backend package. | ai | |
| phantom-deps | phantom-dep:archiver | AI (phantom-deps): archiver is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:mockdate | AI (phantom-deps): mockdate is a declared dep used in test helpers; phantom-dep heuristic false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes email attachment content in a seed/migration file; no code execution, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@bwip-js/node | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-ses | AI (phantom-deps): Declared runtime dep; framework-scoped, loaded by convention as noted by analyzer. | ai | |
| phantom-deps | phantom-dep:handlebars | AI (phantom-deps): handlebars is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): luxon is a declared runtime dep; phantom-dep heuristic false positive for this monorepo. | ai |
Versions (showing 51 of 157)
| Version | Deps | Published |
|---|---|---|
| 2.137.4 | 45 / 10 | |
| 2.137.3 | 45 / 10 | |
| 2.137.2 | 45 / 10 | |
| 2.137.1 | 45 / 10 | |
| 2.137.0 | 45 / 10 | |
| 2.136.3 | 44 / 11 | |
| 2.136.2 | 44 / 11 | |
| 2.122.1 | 44 / 11 | |
| 2.122.0 | 44 / 11 | |
| 2.120.2 | 32 / 8 | |
| 2.107.2 | 32 / 8 | |
| 2.82.0 | 29 / 8 | |
| 2.81.0 | 29 / 8 | |
| 2.80.1 | 29 / 8 | |
| 2.80.0 | 29 / 8 | |
| 2.79.8 | 29 / 8 | |
| 2.79.7 | 29 / 8 | |
| 2.79.6 | 29 / 8 | |
| 2.79.5 | 29 / 8 | |
| 2.79.4 | 29 / 8 | |
| 2.79.3 | 29 / 8 | |
| 2.79.2 | 29 / 8 | |
| 2.79.1 | 29 / 8 | |
| 2.79.0 | 29 / 8 | |
| 2.78.4 | 29 / 8 | |
| 2.78.3 | 29 / 8 | |
| 2.78.2 | 29 / 8 | |
| 2.78.1 | 29 / 8 | |
| 2.78.0 | 29 / 8 | |
| 2.77.5 | 29 / 8 | |
| 2.77.4 | 29 / 8 | |
| 2.77.3 | 29 / 8 | |
| 2.77.2 | 29 / 8 | |
| 2.77.1 | 29 / 8 | |
| 2.77.0 | 29 / 8 | |
| 2.76.0 | 29 / 8 | |
| 2.75.2 | 29 / 8 | |
| 2.75.1 | 29 / 8 | |
| 2.75.0 | 29 / 8 | |
| 2.74.0 | 29 / 8 | |
| 2.73.3 | 29 / 8 | |
| 2.73.2 | 29 / 8 | |
| 2.73.1 | 29 / 8 | |
| 2.73.0 | 29 / 8 | |
| 2.72.0 | 29 / 8 | |
| 2.71.0 | 29 / 8 | |
| 2.70.0 | 29 / 8 | |
| 2.69.0 | 29 / 8 | |
| 2.68.0 | 29 / 8 | |
| 2.67.0 | 29 / 8 | |
| 2.66.0 | 29 / 8 |
v2.137.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.74.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bjarneba) than the most recent previously approved version (simonbackx) on 2025-02-07, but bjarneba is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.73.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bjarneba) than the most recent previously approved version (simonbackx) on 2025-01-16, but bjarneba is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.69.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (simonbackx) than the most recent previously approved version (bjarneba) on 2025-01-15, but simonbackx is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.67.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bjarneba) than the most recent previously approved version (simonbackx) on 2025-01-14, but bjarneba is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.66.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bjarneba) than the most recent previously approved version (simonbackx) on 2025-01-08, but bjarneba is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.