@squidcloud/slack-client
Squid Slack Client
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Webpack-bundled package; deps resolved at build time, not via direct import statements. | ai | |
| phantom-deps | phantom-dep:assertic | AI (phantom-deps): Webpack-bundled package; deps resolved at build time, not via direct import statements. | ai | |
| phantom-deps | phantom-dep:@slack/bolt | AI (phantom-deps): Webpack-bundled package; deps resolved at build time, not via direct import statements. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.0.482 | 4 / 0 | |
| 1.0.481 | 4 / 0 | |
| 1.0.479 | 4 / 0 | |
| 1.0.478 | 4 / 0 | |
| 1.0.477 | 4 / 0 | |
| 1.0.476 | 4 / 0 | |
| 1.0.475 | 4 / 0 | |
| 1.0.474 | 4 / 0 | |
| 1.0.473 | 4 / 0 | |
| 1.0.472 | 4 / 0 | |
| 1.0.471 | 4 / 0 | |
| 1.0.470 | 4 / 0 | |
| 1.0.469 | 4 / 0 | |
| 1.0.468 | 4 / 0 | |
| 1.0.467 | 4 / 0 | |
| 1.0.466 | 4 / 0 | |
| 1.0.465 | 4 / 0 | |
| 1.0.462 | 4 / 0 | |
| 1.0.458 | 4 / 0 | |
| 1.0.455 | 4 / 0 | |
| 1.0.454 | 4 / 0 | |
| 1.0.453 | 4 / 0 | |
| 1.0.452 | 4 / 0 | |
| 1.0.447 | 4 / 0 | |
| 1.0.440 | 4 / 0 | |
| 1.0.426 | 4 / 0 | |
| 1.0.421 | 4 / 0 | |
| 1.0.419 | 4 / 0 | |
| 1.0.416 | 4 / 0 | |
| 1.0.415 | 4 / 0 | |
| 1.0.414 | 4 / 0 | |
| 1.0.411 | 4 / 0 | |
| 1.0.409 | 4 / 0 |
v1.0.482
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 (mfursov) than the most recent previously approved version (robbert_squid) on 2026-07-17, but mfursov 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.
v1.0.481
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 (robbert_squid) than the most recent previously approved version (wynnch-squid-ai) on 2026-07-15, but robbert_squid 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.
v1.0.479
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 (wynnch-squid-ai) than the most recent previously approved version (mfursov) on 2026-07-13, but wynnch-squid-ai 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.
v1.0.478
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 (mfursov) than the most recent previously approved version (squid.cloud) on 2026-07-12, but mfursov 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.
v1.0.477
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.476
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.475
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 (squid.cloud) than the most recent previously approved version (victor-at-squid) on 2026-06-30, but squid.cloud 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.
v1.0.474
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 (squid.cloud) than the most recent previously approved version (victor-at-squid) on 2026-06-30, but squid.cloud 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.
v1.0.473
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.