← Home

@backstage/backend-app-api

npm Repository Homepage

Core API used by Backstage backend apps

13
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
dependencies unvetted-dep:@backstage/config AI (dependencies): Same-org @backstage scoped dependency; part of the official Backstage monorepo release cycle. Not a security concern. ai
dependencies unvetted-dep:@backstage/errors AI (dependencies): Same-org @backstage scoped dependency; part of the official Backstage monorepo release cycle. Not a security concern. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): Same-org @backstage scoped dependency; part of the official Backstage monorepo release cycle. Not a security concern. ai
phantom-deps phantom-dep:@backstage/config AI (phantom-deps): @backstage/config is declared for config schema purposes (configSchema field); not being directly imported in source is expected for this package. ai

Versions (showing 13 of 13)

Version Deps Published
1.7.0 3 / 3
1.6.1 3 / 3
1.6.0 3 / 3
1.5.0 3 / 3
1.4.1 3 / 3
1.4.0 3 / 3
1.3.0 3 / 3
1.2.8 3 / 3
1.2.7 3 / 3
1.2.6 3 / 3
1.2.5 3 / 3
1.2.4 3 / 3
1.2.3 3 / 3

v1.7.0

1 finding
LOW No provenance attestation provenance

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

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

v1.2.8

1 finding
LOW No provenance attestation provenance

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

v1.2.7

1 finding
LOW No provenance attestation provenance

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

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

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

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

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