@backstage/plugin-auth-backend-module-bitbucket-provider Apache-2.0 13 versions

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

npm Repository

The bitbucket-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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:passport-bitbucket-oauth2	AI (dependencies): passport-bitbucket-oauth2 is the expected Passport.js strategy for Bitbucket OAuth2; its use is inherent to this package's purpose as a Bitbucket auth provider.	ai	2026/04/27
bogus-package	bogus-package	AI (bogus-package): Backstage monorepo sub-packages routinely have minimal READMEs and no keywords; this is a structural pattern, not a spam indicator.	ai	2026/04/25
phantom-deps	phantom-dep:express	AI (phantom-deps): express is declared as a dependency in this Backstage auth plugin and used via config/type references; phantom-dep flag is a false positive for this package structure.	ai	2026/04/25
phantom-deps	phantom-dep:passport	AI (phantom-deps): passport is a standard dependency for Backstage auth provider plugins; phantom-dep flag is a false positive for this package structure.	ai	2026/04/25

Versions (showing 13 of 13)

Version	Deps	Published
0.3.15	6 / 6	2026-05-19
0.3.14	6 / 6	2026-04-14
0.3.13	6 / 6	2026-03-17
0.3.12	6 / 6	2026-02-17
0.3.11	6 / 6	2026-01-28
0.3.10	6 / 6	2025-12-16
0.3.9	6 / 6	2025-11-18
0.3.8	6 / 6	2025-10-14
0.3.7	6 / 6	2025-09-16
0.3.6	6 / 6	2025-08-19
0.3.5	6 / 6	2025-07-15
0.3.4	6 / 6	2025-06-17
0.3.3	6 / 6	2025-05-20

v0.3.15

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

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

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