@backstage/plugin-events-backend-module-kafka
The kafka backend module for the events 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:kafkajs | AI (dependencies): kafkajs is the canonical Node.js Kafka client and the expected dependency for a Kafka events backend module. This is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official Backstage monorepo package; lack of Sigstore provenance is common and not a security concern for this well-established scoped package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.4 | 5 / 3 | |
| 0.3.3 | 5 / 3 | |
| 0.3.2 | 5 / 3 | |
| 0.3.1 | 5 / 3 | |
| 0.3.0 | 5 / 3 | |
| 0.2.0 | 5 / 3 | |
| 0.1.5 | 5 / 3 | |
| 0.1.4 | 5 / 3 | |
| 0.1.3 | 5 / 3 | |
| 0.1.2 | 5 / 3 | |
| 0.1.1 | 6 / 3 | |
| 0.1.0 | 6 / 3 |
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.