@slack/socket-mode
Official library for using the Slack Platform's Socket Mode API
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:finity | AI (dependencies): finity is a long-standing FSM dependency of this SDK; stable usage across versions. | ai | |
| phantom-deps | phantom-dep:finity | AI (phantom-deps): finity is a runtime dep used indirectly via state machine config; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): @types/ws is a TypeScript type declaration for the ws library; declaring it in dependencies for type resolution is a common and legitimate pattern in TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a standard TypeScript type declaration; declaring it in dependencies is a common pattern for Node.js TypeScript packages to ensure consumers get correct types. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 6 / 5 | |
| 2.0.6 | 6 / 5 | |
| 2.0.5 | 6 / 20 | |
| 2.0.4 | 6 / 18 | |
| 2.0.3 | 6 / 16 | |
| 2.0.2 | 6 / 14 | |
| 2.0.1 | 7 / 21 | |
| 2.0.0 | 7 / 21 |
v2.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.