@slack/bolt
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): False positive — @slack/bolt is the official Slack app framework by Slack Technologies. The scoped name bears no meaningful similarity to 'got'; the Levenshtein comparison ignores the @slack/ scope. | ai | |
| dependencies | unvetted-dep:@slack/oauth | AI (dependencies): First-party Slack SDK package from the same @slack npm scope; legitimate dependency for this official Slack framework. | ai | |
| dependencies | unvetted-dep:@slack/types | AI (dependencies): First-party Slack SDK package from the same @slack npm scope; legitimate dependency for this official Slack framework. | ai | |
| dependencies | unvetted-dep:@slack/logger | AI (dependencies): First-party Slack SDK package from the same @slack npm scope; legitimate dependency for this official Slack framework. | ai | |
| dependencies | unvetted-dep:@slack/web-api | AI (dependencies): First-party Slack SDK package from the same @slack npm scope; legitimate dependency for this official Slack framework. | ai | |
| dependencies | unvetted-dep:@slack/socket-mode | AI (dependencies): First-party Slack SDK package from the same @slack npm scope; legitimate dependency for this official Slack framework. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.7.3 | 10 / 19 | |
| 4.7.2 | 10 / 19 | |
| 4.7.1 | 10 / 19 | |
| 4.7.0 | 10 / 18 | |
| 4.6.0 | 10 / 18 | |
| 4.5.0 | 10 / 18 | |
| 4.4.0 | 10 / 17 | |
| 4.3.0 | 10 / 17 |
v4.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (e-zim) than the most recent previously approved version (slackhq) on 2025-10-07, but e-zim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.