@backstage/plugin-mcp-actions-backend Apache-2.0 14 versions

@backstage/plugin-mcp-actions-backend

npm Repository

14

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 — the axios compromise (March 2026) relied on exactly this gap.

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 scoped package from the Backstage monorepo; legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/errors	AI (dependencies): Official @backstage scoped package from the Backstage monorepo; legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/backend-plugin-api	AI (dependencies): Official @backstage scoped package from the Backstage monorepo; legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-catalog-node	AI (dependencies): Official @backstage scoped package from the Backstage monorepo; legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:express-promise-router	AI (dependencies): Well-known, widely-used express middleware package; no security concerns.	ai	2026/04/25
phantom-deps	phantom-dep:zod	AI (phantom-deps): Backstage monorepo build pattern; declared for config schema purposes, not directly imported in all files.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/types	AI (phantom-deps): Same-org Backstage package; phantom dep pattern is expected in Backstage monorepo builds.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/config	AI (phantom-deps): Same-org Backstage package; phantom dep pattern is expected in Backstage monorepo builds.	ai	2026/04/25
phantom-deps	phantom-dep:@cfworker/json-schema	AI (phantom-deps): Referenced in config files per Backstage build tooling patterns; not a security concern.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/catalog-client	AI (phantom-deps): Same-org Backstage package; phantom dep pattern is expected in Backstage monorepo builds.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/plugin-catalog-node	AI (phantom-deps): Same-org Backstage package; phantom dep pattern is expected in Backstage monorepo builds.	ai	2026/04/25

Versions (showing 14 of 14)

Version	Deps	Published
0.1.13	12 / 6	2026-05-19
0.1.12	12 / 6	2026-04-14
0.1.11	12 / 6	2026-04-07
0.1.10	12 / 6	2026-03-17
0.1.9	10 / 6	2026-02-17
0.1.8	11 / 3	2026-01-28
0.1.7	11 / 3	2026-01-20
0.1.6	11 / 3	2025-12-16
0.1.5	10 / 3	2025-11-18
0.1.4	10 / 3	2025-10-14
0.1.3	10 / 3	2025-09-16
0.1.2	10 / 3	2025-08-19
0.1.1	10 / 3	2025-07-15
0.1.0	10 / 3	2025-06-17

v0.1.13

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

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