@cedarjs/auth-clerk-api
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
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@clerk/clerk-sdk-node | AI (dependencies): Official Clerk Node SDK; well-established package, routine replacement for @clerk/backend. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dep swap from @clerk/backend to @clerk/clerk-sdk-node is a known Clerk SDK rename; not a suspicious addition. | ai | |
| npm-metadata | no-description | AI (npm-metadata): CedarJS monorepo package; missing description is a cosmetic issue, not a risk indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established CedarJS package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 5.0.3 | 1 / 8 | |
| 5.0.2 | 1 / 8 | |
| 5.0.1 | 1 / 8 | |
| 5.0.0 | 1 / 8 | |
| 4.2.0 | 1 / 9 | |
| 4.1.0 | 1 / 9 | |
| 4.0.0 | 1 / 9 | |
| 3.1.1 | 1 / 9 | |
| 3.1.0 | 1 / 9 | |
| 3.0.0 | 1 / 9 | |
| 2.8.1 | 1 / 9 | |
| 2.8.0 | 1 / 9 | |
| 2.7.0 | 1 / 9 | |
| 2.6.0 | 1 / 9 | |
| 2.5.1 | 1 / 9 | |
| 2.5.0 | 1 / 9 | |
| 2.4.1 | 1 / 9 | |
| 2.4.0 | 1 / 9 | |
| 2.3.0 | 1 / 9 | |
| 2.2.1 | 1 / 9 | |
| 2.2.0 | 1 / 9 | |
| 2.1.1 | 1 / 9 | |
| 2.1.0 | 1 / 9 | |
| 2.0.3 | 1 / 9 | |
| 2.0.2 | 1 / 9 | |
| 2.0.1 | 1 / 9 | |
| 2.0.0 | 1 / 9 | |
| 1.1.2 | 1 / 9 | |
| 1.1.1 | 1 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.0 | 1 / 9 |
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.