@backstage/cli-module-migrate No license 3 versions

@backstage/cli-module-migrate

npm Repository Homepage

Versions

—

License

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/release-manifests	AI (dependencies): First-party @backstage scoped package; part of the official Backstage monorepo ecosystem. Stable accept for this package.	ai	2026/04/27
provenance	no-provenance	AI (provenance): Backstage publishes many packages without Sigstore provenance; this is consistent across the org and not a security signal for this package.	ai	2026/04/25

Versions (showing 3 of 3)

Version	Deps	Published
0.1.2	12 / 6	2026-05-19
0.1.1	12 / 6	2026-04-14
0.1.0	12 / 6	2026-03-17

v0.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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.