← Home

@cedarjs/auth-dbauth-middleware

npm Repository Homepage

```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): Internal cedarjs monorepo sibling package; not a third-party risk. ai
provenance no-provenance AI (provenance): Established monorepo package; lack of provenance is common and not a risk signal here. ai

Versions (showing 32 of 32)

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

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.