← Home

@backstage/repo-tools

CLI for Backstage repo tooling

17
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

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): @prettier/sync is an official Prettier package; addition is benign and consistent with this CLI's formatting use case. ai
dependencies unvetted-dep:yaml-diff-patch AI (dependencies): yaml-diff-patch is a small YAML patching utility; appropriate for a repo tooling package. ai
dependencies unvetted-dep:knip AI (dependencies): knip is a well-known dead-code/unused-exports finder; legitimate dev tooling dependency for a repo-tools CLI. ai
dependencies unvetted-dep:@microsoft/api-documenter AI (dependencies): Part of Microsoft's API toolchain, consistent with the already-approved @microsoft/api-extractor dependency in this package. ai
dependencies unvetted-dep:@useoptic/openapi-utilities AI (dependencies): Optic's OpenAPI utilities; legitimate OpenAPI tooling used by this repo-tools CLI. ai
dependencies unvetted-dep:@apisyouwonthate/style-guide AI (dependencies): APIs You Won't Hate style guide for Spectral; legitimate OpenAPI linting ruleset. ai
dependencies unvetted-dep:@stoplight/spectral-rulesets AI (dependencies): Stoplight Spectral rulesets; standard OpenAPI linting component used alongside other @stoplight packages. ai
dependencies unvetted-dep:@stoplight/spectral-formatters AI (dependencies): Stoplight Spectral formatters; standard OpenAPI linting component, consistent with other @stoplight deps. ai
dependencies unvetted-dep:@openapitools/openapi-generator-cli AI (dependencies): OpenAPI Generator CLI; well-known code generation tool appropriate for a repo-tools CLI. ai
phantom-deps phantom-dep:@electric-sql/pglite AI (phantom-deps): pglite is used as a runtime dependency for database tooling features; referenced in config files is expected for this package. ai
phantom-deps phantom-dep:@backstage/catalog-model AI (phantom-deps): Same-org Backstage dependency; phantom detection is a false positive for this monorepo CLI tool. ai
phantom-deps phantom-dep:@stoplight/spectral-runtime AI (phantom-deps): Spectral runtime is a transitive/config-level dependency for OpenAPI linting; phantom detection is a false positive here. ai
phantom-deps phantom-dep:@openapitools/openapi-generator-cli AI (phantom-deps): openapi-generator-cli is invoked as a CLI tool via config, not directly imported; phantom detection is a false positive for this tooling package. ai
provenance no-provenance AI (provenance): Backstage packages historically do not publish with Sigstore provenance; this is consistent across the ecosystem and not a risk signal. ai
phantom-deps phantom-dep:is-glob AI (phantom-deps): is-glob is a utility dependency used in config/helper contexts; phantom detection is a false positive for this CLI tooling package. ai
phantom-deps phantom-dep:knip AI (phantom-deps): knip is declared as a dependency and used as a CLI tool invoked via config; not directly imported in source is expected for this tooling package. ai

Versions (showing 17 of 17)

Version Deps Published
0.17.2 44 / 7
0.17.1 44 / 7
0.17.0 44 / 7
0.16.5 44 / 7
0.16.4 44 / 7
0.16.3 43 / 7
0.16.2 43 / 7
0.16.1 43 / 7
0.16.0 43 / 7
0.15.4 43 / 7
0.15.3 43 / 7
0.15.2 43 / 7
0.15.1 43 / 7
0.15.0 43 / 7
0.14.0 43 / 7
0.13.4 41 / 7
0.13.3 41 / 7

v0.17.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.17.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.17.0

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

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

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.15.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.15.3

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.15.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.15.1

1 finding
INFO No provenance attestation provenance

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

v0.15.0

1 finding
INFO No provenance attestation provenance

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

v0.14.0

1 finding
INFO No provenance attestation provenance

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

v0.13.4

1 finding
INFO No provenance attestation provenance

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

v0.13.3

1 finding
INFO No provenance attestation provenance

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