← Home

@backstage/plugin-auth-backend-module-azure-easyauth-provider

npm Repository

The azure-easyauth-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 commonly have minimal READMEs and no keywords; documentation lives in the main backstage/backstage repo. Not a spam indicator for this package. ai
phantom-deps phantom-dep:express AI (phantom-deps): Express is a peer/framework dependency in Backstage backend plugins, loaded by convention through the framework. Stable false positive for this package. ai
phantom-deps phantom-dep:@types/passport AI (phantom-deps): Type-only package used for TypeScript type augmentation in the auth plugin context; framework-scoped loading is expected. ai
phantom-deps phantom-dep:@backstage/catalog-model AI (phantom-deps): Same-org Backstage package; may be used transitively or via re-exports within the Backstage auth framework. Expected pattern for this package. ai

Versions (showing 13 of 13)

Version Deps Published
0.2.20 9 / 3
0.2.19 9 / 3
0.2.18 9 / 3
0.2.17 9 / 3
0.2.16 9 / 3
0.2.15 9 / 3
0.2.14 9 / 3
0.2.13 9 / 3
0.2.12 9 / 3
0.2.11 9 / 3
0.2.10 9 / 3
0.2.9 9 / 3
0.2.8 9 / 3

v0.2.20

1 finding
LOW No provenance attestation provenance

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

v0.2.19

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

1 finding
LOW No provenance attestation provenance

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

v0.2.12

1 finding
LOW No provenance attestation provenance

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

v0.2.11

1 finding
LOW No provenance attestation provenance

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

v0.2.10

1 finding
LOW No provenance attestation provenance

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

v0.2.9

1 finding
LOW No provenance attestation provenance

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

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