@backstage/plugin-notifications-backend
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:yn | AI (phantom-deps): Config-driven dependency; stable pattern in Backstage plugins. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Config-driven logging; stable pattern in Backstage backend plugins. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-client | AI (phantom-deps): Backstage framework plugin dependency; stable pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Backstage framework plugin dependency; stable pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-events-node | AI (phantom-deps): Backstage framework plugin dependency; stable pattern. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Official @backstage/* package from the Backstage monorepo; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-signals-node | AI (dependencies): Official @backstage/* package from the Backstage monorepo; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:knex | AI (dependencies): knex is a well-known SQL query builder with millions of weekly downloads; its use in a backend plugin is expected and legitimate. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-notifications-common | AI (dependencies): Official @backstage/* package from the Backstage monorepo; sibling package in the notifications plugin family. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-notifications-node | AI (dependencies): Official @backstage/* package from the Backstage monorepo; sibling package in the notifications plugin family. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official @backstage/* package from the Backstage monorepo; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official @backstage/* package from the Backstage monorepo; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:express-promise-router | AI (dependencies): Well-known Express middleware with a long history; legitimate use in a backend plugin. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage/* package from the Backstage monorepo; core API dependency for backend plugins. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.6.5 | 13 / 10 | |
| 0.6.4 | 14 / 10 | |
| 0.6.3 | 14 / 10 | |
| 0.6.2 | 14 / 10 | |
| 0.6.1 | 14 / 10 | |
| 0.6.0 | 14 / 10 | |
| 0.5.11 | 14 / 10 | |
| 0.5.10 | 18 / 11 | |
| 0.5.9 | 18 / 11 | |
| 0.5.8 | 18 / 11 | |
| 0.5.7 | 18 / 11 | |
| 0.5.6 | 19 / 11 |
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.