← Home

@backstage/backend-plugin-api

14
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 — 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
phantom-deps phantom-dep:@types/luxon AI (phantom-deps): Type definitions for runtime dependency luxon; legitimate TypeScript framework pattern. ai
phantom-deps phantom-dep:@types/express AI (phantom-deps): Type definitions for runtime dependency express; legitimate TypeScript framework pattern. ai
phantom-deps phantom-dep:@types/json-schema AI (phantom-deps): Type definitions for runtime dependency json-schema; legitimate TypeScript framework pattern. ai
phantom-deps phantom-dep:@backstage/plugin-auth-node AI (phantom-deps): Same-org peer dependency; legitimate pattern in Backstage ecosystem. ai

Versions (showing 14 of 14)

Version Deps Published
1.9.1 14 / 2
1.9.0 14 / 2
1.8.0 14 / 2
1.7.0 14 / 2
1.6.2 14 / 2
1.6.1 14 / 2
1.6.0 14 / 2
1.5.0 14 / 2
1.4.4 14 / 2
1.4.3 14 / 2
1.4.2 14 / 2
1.4.1 14 / 2
1.4.0 14 / 2
1.3.1 11 / 2

v1.9.1

1 finding
LOW No provenance attestation provenance

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

v1.9.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.

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

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