@activepieces/piece-slack
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:openai | AI (phantom-deps): Config-referenced integration dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:replicate | AI (phantom-deps): Config-referenced integration dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@anthropic-ai/sdk | AI (phantom-deps): Config-referenced integration dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Transitive dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Transitive dependency used via @slack/web-api; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): Transitive dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge-ts | AI (phantom-deps): Transitive dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Transitive dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Transitive dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Transitive dependency; stable pattern for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 7 / 0 | |
| 0.16.5 | 7 / 0 | |
| 0.16.1 | 117 / 0 | |
| 0.16.0 | 117 / 0 | |
| 0.15.0 | 7 / 0 | |
| 0.14.2 | 7 / 0 | |
| 0.14.1 | 7 / 0 | |
| 0.14.0 | 7 / 0 | |
| 0.13.0 | 7 / 0 | |
| 0.12.7 | 7 / 0 | |
| 0.12.6 | 7 / 0 | |
| 0.12.5 | 7 / 0 | |
| 0.12.4 | 7 / 0 | |
| 0.12.3 | 17 / 0 | |
| 0.12.2 | 17 / 0 | |
| 0.12.1 | 18 / 0 | |
| 0.12.0 | 18 / 0 | |
| 0.11.7 | 18 / 0 | |
| 0.11.6 | 18 / 0 | |
| 0.11.5 | 18 / 0 | |
| 0.11.4 | 18 / 0 | |
| 0.11.3 | 18 / 0 | |
| 0.11.2 | 17 / 0 | |
| 0.11.1 | 16 / 0 | |
| 0.11.0 | 16 / 0 | |
| 0.10.19 | 15 / 0 | |
| 0.10.18 | 15 / 0 | |
| 0.10.17 | 15 / 0 | |
| 0.10.16 | 15 / 0 | |
| 0.10.15 | 14 / 0 | |
| 0.10.14 | 14 / 0 | |
| 0.10.13 | 14 / 0 | |
| 0.10.11 | 14 / 0 | |
| 0.10.10 | 14 / 0 | |
| 0.10.9 | 15 / 0 | |
| 0.10.8 | 15 / 0 | |
| 0.10.7 | 15 / 0 | |
| 0.10.6 | 15 / 0 | |
| 0.10.5 | 21 / 0 | |
| 0.10.4 | 21 / 0 | |
| 0.10.3 | 21 / 0 | |
| 0.10.2 | 20 / 0 | |
| 0.10.1 | 20 / 0 | |
| 0.10.0 | 20 / 0 | |
| 0.9.5 | 20 / 0 | |
| 0.9.4 | 20 / 0 | |
| 0.9.3 | 20 / 0 | |
| 0.9.2 | 20 / 0 | |
| 0.9.1 | 18 / 0 | |
| 0.9.0 | 18 / 0 | |
| 0.8.6 | 18 / 0 |
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.