@botpress/cognitive
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Botpress org migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-level transition to automated publishing; not indicative of takeover given SLSA attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org publishing workflow change; SLSA provenance confirms legitimate CI publish. | ai | |
| phantom-deps | phantom-dep:exponential-backoff | AI (phantom-deps): exponential-backoff is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 2 / 9 | |
| 1.0.2 | 2 / 9 | |
| 1.0.1 | 2 / 9 | |
| 1.0.0 | 2 / 9 | |
| 0.6.2 | 2 / 13 | |
| 0.6.1 | 2 / 13 | |
| 0.6.0 | 2 / 12 | |
| 0.5.5 | 2 / 12 | |
| 0.5.4 | 2 / 12 | |
| 0.5.3 | 2 / 12 | |
| 0.5.2 | 2 / 12 | |
| 0.5.1 | 2 / 12 | |
| 0.5.0 | 2 / 12 | |
| 0.4.7 | 2 / 12 | |
| 0.4.6 | 2 / 12 | |
| 0.4.5 | 2 / 12 | |
| 0.4.4 | 2 / 12 | |
| 0.4.3 | 2 / 12 | |
| 0.4.2 | 2 / 12 | |
| 0.4.1 | 2 / 12 | |
| 0.4.0 | 2 / 12 | |
| 0.3.18 | 2 / 12 | |
| 0.3.17 | 2 / 12 | |
| 0.3.16 | 2 / 12 | |
| 0.3.15 | 2 / 12 | |
| 0.3.14 | 2 / 12 | |
| 0.3.13 | 2 / 12 | |
| 0.3.12 | 2 / 12 | |
| 0.3.11 | 2 / 12 | |
| 0.3.10 | 2 / 12 | |
| 0.3.9 | 2 / 12 | |
| 0.3.8 | 2 / 12 | |
| 0.3.7 | 2 / 12 | |
| 0.3.6 | 2 / 12 | |
| 0.3.5 | 2 / 12 | |
| 0.3.4 | 2 / 12 | |
| 0.3.3 | 2 / 12 | |
| 0.3.2 | 2 / 12 | |
| 0.3.1 | 2 / 11 | |
| 0.3.0 | 2 / 11 | |
| 0.2.1 | 2 / 11 | |
| 0.2.0 | 2 / 11 | |
| 0.1.50 | 2 / 11 | |
| 0.1.49 | 2 / 11 | |
| 0.1.48 | 2 / 11 | |
| 0.1.47 | 2 / 11 | |
| 0.1.46 | 2 / 11 | |
| 0.1.45 | 2 / 11 | |
| 0.1.44 | 2 / 11 | |
| 0.1.43 | 2 / 11 | |
| 0.1.42 | 2 / 11 | |
| 0.1.41 | 2 / 11 | |
| 0.1.40 | 2 / 11 | |
| 0.1.39 | 2 / 11 | |
| 0.1.38 | 2 / 11 | |
| 0.1.37 | 2 / 11 | |
| 0.1.36 | 2 / 11 | |
| 0.1.35 | 2 / 11 | |
| 0.1.34 | 2 / 11 | |
| 0.1.33 | 2 / 11 | |
| 0.1.32 | 2 / 11 | |
| 0.1.31 | 2 / 11 | |
| 0.1.30 | 2 / 11 | |
| 0.1.29 | 2 / 11 | |
| 0.1.28 | 2 / 11 | |
| 0.1.27 | 2 / 11 | |
| 0.1.26 | 2 / 11 | |
| 0.1.25 | 2 / 11 | |
| 0.1.24 | 2 / 11 | |
| 0.1.23 | 2 / 11 | |
| 0.1.22 | 2 / 11 | |
| 0.1.21 | 2 / 11 | |
| 0.1.20 | 2 / 11 | |
| 0.1.19 | 2 / 11 | |
| 0.1.18 | 2 / 11 | |
| 0.1.17 | 2 / 11 | |
| 0.1.16 | 2 / 11 | |
| 0.1.15 | 2 / 11 | |
| 0.1.14 | 2 / 11 | |
| 0.1.13 | 2 / 11 | |
| 0.1.12 | 2 / 11 | |
| 0.1.11 | 2 / 11 | |
| 0.1.10 | 2 / 11 | |
| 0.1.9 | 2 / 11 | |
| 0.1.8 | 2 / 11 | |
| 0.1.7 | 2 / 11 | |
| 0.1.6 | 2 / 11 | |
| 0.1.5 | 2 / 11 | |
| 0.1.4 | 2 / 11 | |
| 0.1.3 | 2 / 11 | |
| 0.1.2 | 2 / 11 | |
| 0.1.1 | 2 / 11 | |
| 0.1.0 | 2 / 11 |
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.