← Home

@backstage/plugin-user-settings-backend

The Backstage backend plugin to manage user settings

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established Backstage monorepo package with 1300+ versions; lack of provenance is consistent across the ecosystem and not a risk signal here. ai
dependencies unvetted-dep:@backstage/plugin-user-settings-common AI (dependencies): Sibling package in the official Backstage monorepo, explicitly listed in pluginPackages. Low risk for this package family. ai
phantom-deps phantom-dep:@backstage/backend-defaults AI (phantom-deps): Same-org Backstage package; also listed in devDependencies. Phantom-dep heuristic is a stable false positive for this package. ai
phantom-deps phantom-dep:already AI (phantom-deps): Backstage monorepo packages commonly declare deps used indirectly or in config; not a security concern for this package. ai
phantom-deps phantom-dep:@backstage/plugin-user-settings-common AI (phantom-deps): Same-org scope dep; indirect usage pattern is normal in Backstage plugin ecosystem. ai
phantom-deps phantom-dep:@backstage/types AI (phantom-deps): Same-org scope dep declared for type resolution in Backstage monorepo build; stable false positive for this package. ai
phantom-deps phantom-dep:@backstage/plugin-auth-node AI (phantom-deps): Same-org scope dep; indirect usage pattern is normal in Backstage plugin ecosystem. ai

Versions (showing 13 of 13)

Version Deps Published
0.4.3 11 / 6
0.4.2 12 / 6
0.4.1 12 / 6
0.4.0 12 / 6
0.3.10 10 / 6
0.3.9 10 / 6
0.3.8 10 / 6
0.3.7 10 / 6
0.3.6 10 / 6
0.3.5 10 / 6
0.3.4 10 / 6
0.3.3 10 / 6
0.3.2 10 / 6

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

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

v0.3.10

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

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

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

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

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

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