← Home

@backstage/plugin-auth-backend-module-bitbucket-server-provider

The bitbucket-server-provider backend module for the auth plugin.

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
bogus-package bogus-package AI (bogus-package): Backstage monorepo packages consistently have minimal READMEs and no keywords; this is a structural pattern of the monorepo, not a spam indicator. ai
phantom-deps phantom-dep:passport AI (phantom-deps): passport is a declared runtime dependency used as a peer/base for passport-oauth2; the phantom-dep flag reflects indirect usage pattern, not a real risk for this auth module. ai

Versions (showing 13 of 13)

Version Deps Published
0.2.15 5 / 7
0.2.14 5 / 7
0.2.13 5 / 7
0.2.12 5 / 7
0.2.11 5 / 7
0.2.10 5 / 7
0.2.9 5 / 7
0.2.8 5 / 7
0.2.7 5 / 7
0.2.6 5 / 7
0.2.5 5 / 7
0.2.4 5 / 7
0.2.3 5 / 7

v0.2.15

1 finding
LOW No provenance attestation provenance

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

v0.2.14

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

1 finding
LOW No provenance attestation provenance

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

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

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