@backstage/plugin-permission-backend-module-allow-all-policy
Allow all policy backend module for the permission 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:@backstage/plugin-auth-node | AI (dependencies): Official @backstage monorepo package; unvetted status reflects pipeline gap, not real risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage monorepo package; unvetted status reflects pipeline gap, not real risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-node | AI (dependencies): Official @backstage monorepo package; unvetted status reflects pipeline gap, not real risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-common | AI (dependencies): Official @backstage monorepo package; unvetted status reflects pipeline gap, not real risk. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Same-org Backstage dep declared but not directly imported; normal for Backstage plugin module architecture. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo-published package with 76.9k weekly downloads and 963-day history; short README and no keywords are standard for Backstage internal modules. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.19 | 4 / 2 | |
| 0.2.18 | 4 / 2 | |
| 0.2.17 | 4 / 2 | |
| 0.2.16 | 4 / 2 | |
| 0.2.15 | 4 / 2 | |
| 0.2.14 | 4 / 2 | |
| 0.2.13 | 4 / 2 | |
| 0.2.12 | 4 / 2 | |
| 0.2.11 | 4 / 2 | |
| 0.2.10 | 4 / 2 | |
| 0.2.9 | 4 / 2 | |
| 0.2.8 | 4 / 2 |
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.