@backstage/plugin-devtools-backend Apache-2.0 48 versions

@backstage/plugin-devtools-backend

npm Repository Homepage

48

Versions

Apache-2.0

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

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): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/config	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/errors	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/cli-common	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:express-promise-router	AI (dependencies): Well-known, widely-used Express middleware; no security concerns.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/config-loader	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/backend-plugin-api	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-devtools-common	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-permission-node	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-permission-common	AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin.	ai	2026/04/25
phantom-deps	phantom-dep:yn	AI (phantom-deps): Declared in package.json as a runtime dep; phantom detection is a false positive for monorepo config usage patterns.	ai	2026/04/25
phantom-deps	phantom-dep:semver	AI (phantom-deps): Declared in package.json as a runtime dep; phantom detection is a false positive for monorepo config usage patterns.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/types	AI (phantom-deps): Official Backstage sibling package; phantom detection false positive for monorepo indirect usage.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/plugin-permission-node	AI (phantom-deps): Official Backstage sibling package; phantom detection false positive for monorepo indirect usage.	ai	2026/04/25

Versions (showing 48 of 48)

Version	Deps	Published
0.5.19	17 / 8	2026-07-14
0.5.18	17 / 8	2026-06-16
0.5.17	17 / 8	2026-05-19
0.5.16	19 / 8	2026-04-14
0.5.15	19 / 8	2026-03-17
0.5.14	19 / 8	2026-02-17
0.5.13	20 / 8	2026-01-20
0.5.12	20 / 8	2025-12-16
0.5.11	20 / 8	2025-11-18
0.5.10	20 / 8	2025-10-14
0.5.9	20 / 8	2025-09-16
0.5.8	20 / 8	2025-08-19
0.5.7	20 / 8	2025-07-15
0.5.6	20 / 8	2025-06-17
0.5.5	20 / 8	2025-05-20
0.5.4	20 / 8	2025-04-15
0.5.3	20 / 8	2025-03-18
0.5.2	20 / 8	2025-02-18
0.5.1	20 / 8	2025-01-14
0.5.0	20 / 8	2024-12-17
0.4.2	22 / 7	2024-11-19
0.4.1	22 / 7	2024-10-15
0.4.0	22 / 7	2024-09-17
0.3.10	22 / 7	2024-08-27
0.3.9	22 / 7	2024-08-20
0.3.8	22 / 7	2024-07-16
0.3.7	22 / 7	2024-06-26
0.3.6	22 / 7	2024-06-19
0.3.5	22 / 7	2024-06-18
0.3.4	22 / 6	2024-05-14
0.3.3	22 / 6	2024-04-16
0.3.2	23 / 6	2024-03-27
0.3.1	23 / 6	2024-03-22
0.3.0	23 / 6	2024-03-19
0.2.10	24 / 6	2024-03-01
0.2.9	24 / 6	2024-02-23
0.2.8	24 / 6	2024-02-22
0.2.7	24 / 6	2024-02-20
0.2.6	24 / 6	2024-01-16
0.2.5	24 / 7	2023-12-19
0.2.4	24 / 7	2023-11-14
0.2.3	24 / 7	2023-10-17
0.2.2	24 / 7	2023-10-04
0.2.1	24 / 7	2023-09-26
0.2.0	24 / 7	2023-09-19
0.1.5	24 / 7	2023-08-23
0.1.4	24 / 7	2023-08-21
0.1.3	24 / 7	2023-08-15

v0.5.19

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

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.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.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.