@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, so a manually published version cannot be tied back to a reviewed commit.
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 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 4 / 4 | |
| 3.8.4 | 4 / 4 | |
| 3.8.0 | 4 / 4 | |
| 3.7.4 | 4 / 4 | |
| 3.7.3 | 4 / 4 | |
| 3.7.1 | 4 / 4 | |
| 3.7.0 | 4 / 4 | |
| 3.6.1 | 4 / 4 | |
| 3.6.0 | 4 / 4 | |
| 3.0.1 | 4 / 5 | |
| 3.0.0 | 4 / 3 |
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.