@slack/web-api
Official library for using the Slack Platform's Web 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:@slack/types | AI (dependencies): @slack/types is a first-party Slack SDK package from the same monorepo (slackapi/node-slack-sdk); always a legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@slack/logger | AI (dependencies): @slack/logger is a first-party Slack SDK package from the same monorepo (slackapi/node-slack-sdk); always a legitimate dependency for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node declared as runtime dep is a known TypeScript pattern for this package; not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/retry | AI (phantom-deps): @types/retry declared as runtime dep is a known TypeScript pattern for this package; not a security concern. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 7.17.0 | 12 / 6 | |
| 7.16.0 | 12 / 6 | |
| 7.15.2 | 12 / 6 | |
| 7.15.1 | 12 / 6 | |
| 7.15.0 | 12 / 6 | |
| 7.14.1 | 12 / 20 | |
| 7.14.0 | 12 / 20 | |
| 7.13.0 | 12 / 21 | |
| 7.11.0 | 12 / 21 | |
| 7.10.0 | 12 / 21 | |
| 7.9.3 | 12 / 19 | |
| 7.9.2 | 12 / 19 | |
| 7.9.1 | 12 / 19 | |
| 7.9.0 | 12 / 19 | |
| 7.8.0 | 12 / 17 | |
| 7.7.0 | 12 / 17 | |
| 7.6.0 | 12 / 17 | |
| 7.5.0 | 12 / 17 | |
| 7.4.0 | 12 / 17 | |
| 7.3.4 | 12 / 25 | |
| 7.3.3 | 12 / 25 | |
| 7.3.2 | 12 / 25 | |
| 7.3.1 | 12 / 25 | |
| 7.3.0 | 12 / 25 | |
| 7.2.0 | 12 / 25 | |
| 7.1.0 | 12 / 25 |
v7.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.15.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.9.1
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 (filmaj) on 2025-03-26, 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.
v7.9.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 (filmaj) on 2025-03-20, 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.
v7.8.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 (slackhq) than the most recent previously approved version (filmaj) on 2024-12-06, but slackhq 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.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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 (misscoded) than the most recent previously approved version (filmaj) on 2024-09-17, but misscoded 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.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
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 (filmaj) on 2024-08-14, 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.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.