@backstage/plugin-permission-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is intentionally listed in dependencies (not devDependencies) in Backstage packages to expose Express types to consumers; this is a stable pattern across the Backstage monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages predate widespread Sigstore provenance adoption; the package's age, download volume, and official repo association make this a stable false positive. | ai |
Versions (showing 82 of 82)
| Version | Deps | Published |
|---|---|---|
| 0.11.2 | 9 / 6 | |
| 0.11.1 | 9 / 6 | |
| 0.11.0 | 9 / 6 | |
| 0.10.12 | 10 / 6 | |
| 0.10.11 | 10 / 6 | |
| 0.10.10 | 10 / 6 | |
| 0.10.9 | 10 / 6 | |
| 0.10.8 | 10 / 6 | |
| 0.10.7 | 10 / 6 | |
| 0.10.6 | 10 / 6 | |
| 0.10.5 | 10 / 6 | |
| 0.10.4 | 10 / 6 | |
| 0.10.3 | 10 / 6 | |
| 0.10.2 | 10 / 6 | |
| 0.10.1 | 10 / 6 | |
| 0.10.0 | 10 / 6 | |
| 0.9.1 | 10 / 6 | |
| 0.9.0 | 10 / 6 | |
| 0.8.8 | 11 / 6 | |
| 0.8.7 | 11 / 6 | |
| 0.8.6 | 11 / 5 | |
| 0.8.5 | 11 / 5 | |
| 0.8.4 | 11 / 5 | |
| 0.8.3 | 11 / 5 | |
| 0.8.2 | 11 / 5 | |
| 0.8.1 | 11 / 5 | |
| 0.8.0 | 11 / 5 | |
| 0.7.32 | 11 / 5 | |
| 0.7.31 | 11 / 5 | |
| 0.7.30 | 11 / 5 | |
| 0.7.29 | 11 / 5 | |
| 0.7.28 | 11 / 5 | |
| 0.7.27 | 11 / 5 | |
| 0.7.26 | 11 / 5 | |
| 0.7.25 | 11 / 5 | |
| 0.7.24 | 11 / 5 | |
| 0.7.23 | 11 / 5 | |
| 0.7.22 | 11 / 5 | |
| 0.7.21 | 11 / 5 | |
| 0.7.20 | 11 / 5 | |
| 0.7.19 | 11 / 5 | |
| 0.7.18 | 11 / 5 | |
| 0.7.17 | 11 / 5 | |
| 0.7.16 | 11 / 5 | |
| 0.7.15 | 11 / 5 | |
| 0.7.14 | 11 / 5 | |
| 0.7.13 | 11 / 5 | |
| 0.7.12 | 11 / 5 | |
| 0.7.11 | 11 / 5 | |
| 0.7.10 | 11 / 5 | |
| 0.7.9 | 11 / 5 | |
| 0.7.8 | 11 / 5 | |
| 0.7.7 | 11 / 5 | |
| 0.7.6 | 10 / 5 | |
| 0.7.5 | 10 / 5 | |
| 0.7.4 | 10 / 5 | |
| 0.7.3 | 10 / 5 | |
| 0.7.2 | 10 / 5 | |
| 0.7.1 | 10 / 5 | |
| 0.7.0 | 10 / 5 | |
| 0.6.5 | 9 / 5 | |
| 0.6.4 | 9 / 4 | |
| 0.6.3 | 9 / 4 | |
| 0.6.2 | 9 / 4 | |
| 0.6.1 | 9 / 4 | |
| 0.6.0 | 9 / 4 | |
| 0.5.5 | 9 / 4 | |
| 0.5.4 | 9 / 4 | |
| 0.5.3 | 9 / 4 | |
| 0.5.2 | 9 / 4 | |
| 0.5.1 | 9 / 4 | |
| 0.5.0 | 9 / 4 | |
| 0.4.3 | 9 / 4 | |
| 0.4.2 | 9 / 4 | |
| 0.4.1 | 9 / 4 | |
| 0.4.0 | 9 / 4 | |
| 0.3.0 | 9 / 4 | |
| 0.2.3 | 7 / 4 | |
| 0.2.2 | 7 / 4 | |
| 0.2.1 | 5 / 3 | |
| 0.2.0 | 5 / 3 | |
| 0.1.0 | 5 / 3 |
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
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.7.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.
v0.4.3
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.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.