← Home

@cedarjs/auth-supabase-middleware

```tsx filename='entry.server.tsx' import type { TagDescriptor } from '@cedarjs/web'

32
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
dependencies unvetted-dep:@cedarjs/web AI (dependencies): First-party sibling package from the same cedarjs monorepo; not an independent risk. ai
provenance no-provenance AI (provenance): Cedarjs monorepo package; provenance absence is common and not a risk indicator here. ai

Versions (showing 32 of 32)

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

v5.0.4

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