@backstage/plugin-signals-node
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party Backstage monorepo package; same org scope, no third-party risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): First-party Backstage monorepo package; same org scope, no third-party risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-events-node | AI (dependencies): First-party Backstage monorepo package; same org scope, no third-party risk. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Declared in package.json dependencies; common Backstage pattern where deps are declared but used indirectly or in type contexts. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in package.json dependencies; common Backstage pattern where deps are declared but used indirectly or in type contexts. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Declared in package.json dependencies; common Backstage pattern where deps are declared but used indirectly or in type contexts. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same org scope; declared in dependencies; standard Backstage plugin pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Same org scope; declared in dependencies; standard Backstage plugin pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage package with 81.9k weekly downloads; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 3 / 2 | |
| 0.2.2 | 3 / 2 | |
| 0.2.1 | 3 / 2 | |
| 0.2.0 | 8 / 2 | |
| 0.1.29 | 8 / 2 | |
| 0.1.28 | 8 / 2 | |
| 0.1.27 | 8 / 2 | |
| 0.1.26 | 8 / 2 | |
| 0.1.25 | 8 / 2 | |
| 0.1.24 | 8 / 2 | |
| 0.1.23 | 8 / 2 | |
| 0.1.22 | 8 / 2 | |
| 0.1.21 | 8 / 2 | |
| 0.1.20 | 8 / 2 | |
| 0.1.19 | 8 / 2 | |
| 0.1.18 | 8 / 2 | |
| 0.1.17 | 8 / 2 | |
| 0.1.16 | 8 / 2 | |
| 0.1.15 | 8 / 2 | |
| 0.1.14 | 8 / 2 | |
| 0.1.13 | 9 / 2 | |
| 0.1.12 | 9 / 2 | |
| 0.1.11 | 9 / 2 | |
| 0.1.10 | 9 / 2 | |
| 0.1.9 | 9 / 2 | |
| 0.1.8 | 9 / 2 | |
| 0.1.7 | 9 / 2 | |
| 0.1.6 | 9 / 2 | |
| 0.1.5 | 9 / 2 | |
| 0.1.4 | 9 / 2 | |
| 0.1.3 | 9 / 2 | |
| 0.1.2 | 9 / 2 | |
| 0.1.1 | 9 / 2 | |
| 0.1.0 | 9 / 2 | |
| 0.0.4 | 9 / 2 | |
| 0.0.3 | 9 / 2 | |
| 0.0.2 | 9 / 2 | |
| 0.0.1 | 9 / 2 |
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.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.