← Home

@quatrain/auth-firebase

npm Repository Homepage

The Firebase Authentication adapter for `@quatrain/auth`.

27
Versions
AGPL-3.0-only
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

crapougnaxelliottlepine

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@quatrain/core AI (phantom-deps): Same-org peer dependency; declared in both peerDependencies and dependencies — not a real phantom dep for this package. ai

Versions (showing 27 of 27)

Version Deps Published
1.2.6 6 / 10
1.2.5 6 / 10
1.2.4 6 / 10
1.2.3 6 / 10
1.2.2 5 / 10
1.2.1 5 / 10
1.1.26 5 / 10
1.1.25 5 / 10
1.1.23 5 / 10
1.1.22 5 / 10
1.1.21 5 / 10
1.1.20 5 / 10
1.1.19 5 / 10
1.1.18 5 / 10
1.1.17 5 / 10
1.1.16 5 / 10
1.1.15 5 / 10
1.1.14 5 / 10
1.1.13 2 / 11
1.1.12 2 / 11
1.1.11 2 / 11
1.1.10 2 / 11
1.1.9 2 / 11
1.1.8 2 / 11
1.1.7 2 / 11
1.1.6 2 / 11
1.1.5 2 / 11

v1.2.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.12

1 finding
LOW No provenance attestation provenance

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

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.10

1 finding
LOW No provenance attestation provenance

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

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.8

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

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.