@itentialopensource/adapter-slack
This adapter integrates with system 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived Itential adapter with 48 versions; infrequent releases are normal for this package family. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Itential adapter-base pattern for loading adapter components; stable across versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Itential adapter-base uses execSync/spawnSync for adapter utilities; documented framework pattern. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework standard setup script; consistent across all adapter versions. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Used in utility scripts, not directly imported in main code; stable false positive. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): Test utility referenced in config, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): Used in config/connectivity scripts, not directly imported in main code; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 15 / 6 | |
| 4.0.1 | 15 / 6 | |
| 4.0.0 | 15 / 6 | |
| 3.7.0 | 15 / 6 | |
| 3.5.0 | 15 / 6 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.