@things-factory/board-service
A service to run dashboard
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Migration file loader pattern in a known monorepo; loads local migration files by path, not user input. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes thumbnail image data for HTTP response; no malicious payload risk in this context. | ai | |
| phantom-deps | phantom-dep:pdfjs-dist | AI (phantom-deps): pdfjs-dist is declared as a runtime dep and referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a new risk signal. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 8 / 0 | |
| 9.2.23 | 8 / 0 | |
| 9.2.22 | 8 / 0 | |
| 9.2.21 | 8 / 0 | |
| 9.2.20 | 8 / 0 | |
| 9.2.19 | 8 / 0 | |
| 9.2.16 | 8 / 0 | |
| 6.4.8 | 8 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.