@things-factory/board-test
Test module for running 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, 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:dynamic-require | AI (semgrep): Migration file loader pattern — requires local resolved file paths, not user-controlled input. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/auth-base | AI (phantom-deps): Same-org monorepo dep; declared but used transitively. Stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 9.2.33 | 4 / 0 | |
| 9.2.31 | 4 / 0 | |
| 9.2.30 | 4 / 0 | |
| 9.2.29 | 4 / 0 | |
| 9.2.28 | 4 / 0 | |
| 9.2.27 | 4 / 0 | |
| 9.2.25 | 4 / 0 | |
| 9.2.24 | 4 / 0 | |
| 9.2.22 | 4 / 0 | |
| 9.2.20 | 4 / 0 | |
| 9.2.19 | 4 / 0 | |
| 9.2.16 | 4 / 0 | |
| 9.2.13 | 4 / 0 | |
| 9.2.5 | 4 / 0 | |
| 9.1.19 | 4 / 0 | |
| 8.0.64 | 4 / 0 | |
| 8.0.63 | 4 / 0 | |
| 4.3.705 | 4 / 0 | |
| 4.3.695 | 4 / 0 | |
| 4.3.689 | 4 / 0 |
v9.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.16
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 (nalshya113) than the most recent previously approved version (heartyoh) on 2026-03-25, but nalshya113 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.
v9.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
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 (nalshya113) than the most recent previously approved version (heartyoh) on 2026-03-06, but nalshya113 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.
v9.1.19
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 (heartyoh) than the most recent previously approved version (horwengliang95) on 2025-11-25, but heartyoh 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.
v8.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.705
2 findingsThis version was published by a different npm account than previous versions on 2025-12-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.695
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 (horwengliang95) than the most recent previously approved version (nalshya113) on 2025-11-21, but horwengliang95 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.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.