@bull-board/h3
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped monorepo package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped monorepo package; Levenshtein match to 'qs' is a false positive. | ai | |
| phantom-deps | phantom-dep:@bull-board/ui | AI (phantom-deps): Same-org UI package served by this adapter; not directly imported but legitimately declared as a dependency. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 4 / 1 | |
| 7.2.0 | 4 / 1 | |
| 7.1.5 | 4 / 1 | |
| 7.1.3 | 4 / 1 | |
| 7.0.0 | 4 / 1 | |
| 6.21.3 | 4 / 1 | |
| 6.21.2 | 4 / 1 | |
| 6.21.1 | 4 / 1 | |
| 6.21.0 | 4 / 1 | |
| 6.20.7 | 4 / 1 | |
| 6.20.6 | 4 / 1 | |
| 6.20.5 | 4 / 1 | |
| 6.20.4 | 4 / 1 | |
| 6.20.3 | 4 / 1 | |
| 6.20.2 | 4 / 1 | |
| 6.20.1 | 4 / 1 | |
| 6.20.0 | 4 / 1 | |
| 6.19.0 | 4 / 1 | |
| 6.18.3 | 4 / 1 | |
| 6.18.2 | 4 / 1 | |
| 6.18.1 | 4 / 1 | |
| 6.18.0 | 4 / 1 | |
| 6.17.0 | 4 / 1 | |
| 6.16.4 | 4 / 1 | |
| 6.16.2 | 4 / 1 | |
| 6.16.1 | 4 / 1 | |
| 6.16.0 | 4 / 1 | |
| 6.15.0 | 4 / 1 | |
| 6.14.2 | 4 / 1 | |
| 6.14.1 | 4 / 1 |
v7.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.