@bull-board/koa
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:got | AI (typosquat): Scoped monorepo package; Levenshtein match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped monorepo package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped monorepo package; Levenshtein match to 'zod' is a false positive. | ai | |
| phantom-deps | phantom-dep:ejs | AI (phantom-deps): ejs is a declared template engine dep used indirectly via koa-views; stable false positive. | ai | |
| phantom-deps | phantom-dep:@bull-board/ui | AI (phantom-deps): Same-org UI assets package; used at runtime by the adapter, not directly imported in JS. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 9 / 4 | |
| 7.2.0 | 9 / 4 | |
| 7.1.5 | 9 / 4 | |
| 7.1.3 | 9 / 4 | |
| 7.0.0 | 9 / 4 | |
| 6.21.3 | 9 / 4 | |
| 6.21.2 | 9 / 4 | |
| 6.21.1 | 9 / 6 | |
| 6.21.0 | 9 / 6 | |
| 6.20.7 | 9 / 6 | |
| 6.20.6 | 9 / 6 | |
| 6.20.5 | 9 / 6 | |
| 6.20.4 | 9 / 6 | |
| 6.20.3 | 9 / 6 | |
| 6.20.2 | 9 / 6 | |
| 6.20.1 | 9 / 6 | |
| 6.20.0 | 9 / 6 | |
| 6.19.0 | 9 / 6 | |
| 6.18.3 | 9 / 6 | |
| 6.18.2 | 9 / 6 | |
| 6.18.1 | 9 / 6 | |
| 6.18.0 | 9 / 6 | |
| 6.17.0 | 9 / 6 | |
| 6.16.4 | 9 / 6 | |
| 6.16.2 | 9 / 6 | |
| 6.16.1 | 9 / 6 | |
| 6.16.0 | 9 / 6 | |
| 6.15.0 | 9 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.