← Home

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

npm Repository

The pinniped-provider backend module for the auth plugin.

12
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 plugin modules consistently have short READMEs and no keywords; this is a structural pattern of the project, not a spam indicator. ai
phantom-deps phantom-dep:@backstage/types AI (phantom-deps): @backstage/types is a first-party same-org dependency; phantom usage is typical for type-only or transitive usage in Backstage monorepo packages. ai

Versions (showing 12 of 12)

Version Deps Published
0.3.14 6 / 11
0.3.13 6 / 11
0.3.12 6 / 11
0.3.11 6 / 11
0.3.10 6 / 11
0.3.9 6 / 11
0.3.8 6 / 11
0.3.7 6 / 11
0.3.6 6 / 11
0.3.5 6 / 11
0.3.4 6 / 11
0.3.3 6 / 11

v0.3.14

1 finding
LOW No provenance attestation provenance

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

v0.3.13

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.