← Home

@backstage/plugin-app-backend

A Backstage backend plugin that serves the Backstage frontend app

25
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

patrikofrebenmarcuseide

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@backstage/config AI (phantom-deps): Same-org monorepo dependency. ai
phantom-deps phantom-dep:yn AI (phantom-deps): Config-file reference, not a real risk. ai
phantom-deps phantom-dep:@types/express AI (phantom-deps): Type-only convention package. ai
phantom-deps phantom-dep:@backstage/types AI (phantom-deps): Same-org scoped dep, benign. ai
phantom-deps phantom-dep:@backstage/plugin-auth-node AI (phantom-deps): Same-org scoped dep, benign. ai
dependencies unvetted-dep:@backstage/config-loader AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
dependencies unvetted-dep:@backstage/plugin-app-node AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
dependencies unvetted-dep:knex AI (dependencies): knex is a well-known SQL query builder; its use in a Backstage backend plugin is expected and legitimate. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
provenance no-provenance AI (provenance): Established Backstage package with 2055 days history and 107k weekly downloads; lack of provenance is common and not a risk signal here. ai
dependencies unvetted-dep:@backstage/plugin-auth-node AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
dependencies unvetted-dep:@backstage/types AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
dependencies unvetted-dep:@backstage/config AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
dependencies unvetted-dep:@backstage/errors AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. ai
dependencies unvetted-dep:express-promise-router AI (dependencies): Well-known Express middleware; expected dependency for a Backstage backend plugin. ai

Versions (showing 25 of 25)

Version Deps Published
0.5.16 15 / 7
0.5.15 15 / 7
0.5.14 15 / 7
0.5.13 16 / 8
0.5.12 16 / 8
0.5.11 16 / 8
0.5.10 16 / 8
0.5.9 16 / 8
0.5.8 16 / 8
0.5.7 16 / 8
0.5.6 16 / 8
0.5.5 16 / 8
0.5.4 16 / 8
0.5.3 16 / 8
0.5.2 16 / 8
0.5.1 16 / 8
0.5.0 16 / 8
0.4.5 17 / 7
0.4.4 17 / 7
0.4.3 18 / 7
0.4.2 18 / 8
0.4.1 18 / 8
0.4.0 18 / 8
0.3.76 18 / 8
0.3.75 18 / 8

v0.5.16

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

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

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

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

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

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

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.5.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.5.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.4.5

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

v0.4.2

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.4.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.4.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.3.76

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

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.