@backstage/plugin-permission-react No license 51 versions

@backstage/plugin-permission-react

npm Repository Homepage

51

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

patrikofrebenmarcuseide

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:cross-fetch	AI (phantom-deps): Likely used in build output/polyfill; not evidence of malicious intent.	ai	2026/07/21
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Type-only convention dependency, expected false positive.	ai	2026/07/21
dependencies	unvetted-dep:@backstage/plugin-permission-common	AI (dependencies): Sibling package from the same Backstage monorepo; always a legitimate dependency for this package.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Scoped monorepo package from the official Backstage project; sparse README and description are expected for sub-packages.	ai	2026/04/25
npm-metadata	no-description	AI (npm-metadata): Backstage monorepo sub-packages routinely omit standalone descriptions; not indicative of malicious intent.	ai	2026/04/25

Versions (showing 51 of 56)

View all versions

Version	Deps	Published
0.5.3	5 / 7	2026-07-14
0.5.2	5 / 7	2026-06-16
0.5.1	5 / 7	2026-05-19
0.5.0	5 / 7	2026-04-14
0.4.41	5 / 8	2026-03-17
0.4.40	4 / 8	2026-02-17
0.4.39	4 / 8	2025-12-16
0.4.38	4 / 8	2025-11-18
0.4.37	4 / 8	2025-10-14
0.4.36	4 / 8	2025-07-15
0.4.35	4 / 8	2025-06-17
0.4.34	4 / 8	2025-05-20
0.4.33	4 / 8	2025-04-15
0.4.32	4 / 8	2025-03-18
0.4.31	4 / 8	2025-02-18
0.4.30	4 / 8	2025-01-14
0.4.29	4 / 8	2024-12-17
0.4.28	4 / 8	2024-11-19
0.4.27	4 / 8	2024-10-15
0.4.26	5 / 4	2024-09-17
0.4.25	5 / 4	2024-08-20
0.4.24	5 / 4	2024-07-16
0.4.23	5 / 4	2024-06-18
0.4.22	5 / 4	2024-04-16
0.4.21	5 / 4	2024-03-19
0.4.20	5 / 4	2024-02-20
0.4.19	5 / 4	2024-01-16
0.4.18	7 / 4	2023-12-19
0.4.17	7 / 4	2023-11-14
0.4.16	7 / 4	2023-10-17
0.4.15	7 / 4	2023-09-19
0.4.14	7 / 4	2023-07-18
0.4.13	7 / 4	2023-06-20
0.4.12	7 / 4	2023-04-18
0.4.11	6 / 4	2023-03-14
0.4.10	6 / 4	2023-02-14
0.4.9	6 / 4	2023-01-17
0.4.8	6 / 4	2022-12-20
0.4.7	6 / 4	2022-11-15
0.4.6	6 / 4	2022-10-18
0.4.5	6 / 4	2022-09-20
0.4.4	7 / 5	2022-08-16
0.4.3	7 / 5	2022-07-19
0.4.2	7 / 5	2022-06-14
0.4.1	7 / 5	2022-05-17
0.4.0	7 / 5	2022-04-19
0.3.4	7 / 5	2022-03-17
0.3.3	7 / 5	2022-03-03
0.3.2	7 / 5	2022-02-24
0.3.1	7 / 5	2022-02-17
0.3.0	6 / 5	2022-01-20

v0.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.4

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.