@midwayjs/bull-board
midway component for bull-board
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@bull-board/ui | AI (dependencies): Known bull-board UI package; stable dependency for this Midway component across versions. | ai | |
| dependencies | unvetted-dep:@bull-board/api | AI (dependencies): Known bull-board API package; stable dependency for this Midway component across versions. | ai | |
| phantom-deps | phantom-dep:@bull-board/ui | AI (phantom-deps): UI package is a static asset dependency referenced via config, not direct import; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component of @midwayjs; sparse README and no standalone repo URL are expected for sub-packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 3 / 6 | |
| 4.0.2 | 3 / 6 | |
| 4.0.1 | 3 / 6 | |
| 4.0.0 | 3 / 6 | |
| 3.20.24 | 3 / 6 | |
| 3.20.23 | 3 / 6 | |
| 3.20.22 | 3 / 6 | |
| 3.20.20 | 3 / 6 | |
| 3.20.19 | 3 / 6 | |
| 3.20.16 | 3 / 6 | |
| 3.20.15 | 3 / 6 | |
| 3.20.13 | 3 / 6 | |
| 3.20.12 | 3 / 6 | |
| 3.20.11 | 3 / 6 | |
| 3.20.7 | 3 / 6 | |
| 3.20.6 | 3 / 6 | |
| 3.20.5 | 3 / 6 |
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.