@backstage/plugin-notifications-backend-module-slack
The slack backend module for the notifications plugin.
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:@slack/bolt | AI (phantom-deps): Slack plugin module; @slack/bolt is a core dependency used indirectly through plugin infrastructure, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@slack/types | AI (phantom-deps): Type definitions for Slack integration; referenced in config and type definitions, not direct source imports. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org Backstage dependency used indirectly through plugin infrastructure; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-notifications-common | AI (phantom-deps): Same-org Backstage dependency used indirectly through plugin infrastructure; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-notifications-node | AI (dependencies): Official @backstage scoped package; direct parent plugin dependency for this notifications module. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official @backstage scoped package; expected dependency for a Backstage plugin module in the backstage monorepo ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo-published package; short README and no keywords are expected patterns for Backstage plugin modules where docs live in the main repo. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-notifications-common | AI (dependencies): Official @backstage scoped package; shared types/interfaces for the notifications plugin family. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official @backstage scoped package; expected dependency for a Backstage plugin module. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage scoped package; core API for Backstage backend plugin modules. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Official @backstage scoped package; expected dependency for catalog integration in Backstage plugins. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 14 / 5 | |
| 0.4.1 | 13 / 6 | |
| 0.4.0 | 13 / 6 | |
| 0.3.1 | 14 / 6 | |
| 0.3.0 | 14 / 6 | |
| 0.2.1 | 14 / 6 | |
| 0.2.0 | 14 / 6 | |
| 0.1.5 | 14 / 6 | |
| 0.1.4 | 14 / 6 | |
| 0.1.3 | 14 / 6 | |
| 0.1.2 | 14 / 6 | |
| 0.1.1 | 14 / 6 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.