@slack/webhook
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 5 / 1 | |
| 7.2.0 | 6 / 1 | |
| 7.1.0 | 3 / 1 | |
| 7.0.9 | 3 / 1 | |
| 7.0.8 | 3 / 1 | |
| 7.0.7 | 3 / 14 | |
| 7.0.6 | 3 / 15 | |
| 7.0.5 | 3 / 11 | |
| 7.0.4 | 3 / 11 | |
| 7.0.3 | 3 / 21 |
v8.0.0
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.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.5
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-03-12, 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.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.