← Home

@cedarjs/auth-supabase-setup

If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P

31
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tobbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): New ecosystem; provenance not yet configured but package is otherwise clean. ai

Versions (showing 31 of 31)

Version Deps Published
5.0.3 1 / 6
5.0.2 1 / 6
5.0.1 1 / 6
5.0.0 1 / 6
4.2.0 1 / 7
4.1.0 1 / 7
4.0.0 1 / 7
3.1.1 1 / 7
3.1.0 1 / 7
3.0.0 1 / 7
2.8.1 1 / 7
2.8.0 1 / 7
2.7.0 1 / 7
2.6.0 1 / 7
2.5.1 1 / 7
2.5.0 1 / 7
2.4.1 1 / 7
2.4.0 1 / 7
2.3.0 1 / 7
2.2.1 1 / 7
2.2.0 1 / 7
2.1.1 1 / 7
2.1.0 1 / 7
2.0.3 1 / 7
2.0.2 1 / 7
2.0.1 1 / 7
2.0.0 1 / 7
1.1.2 1 / 7
1.1.1 1 / 7
1.1.0 1 / 7
1.0.0 1 / 7

v5.0.3

1 finding
INFO No provenance attestation provenance

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

v5.0.2

1 finding
INFO No provenance attestation provenance

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

v5.0.1

1 finding
INFO No provenance attestation provenance

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

v5.0.0

1 finding
INFO No provenance attestation provenance

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