← Home

@cloudflare/workers-oauth-provider

npm Repository Homepage
26
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cf-ci-writedash_service_accountwrangler-publishercfprivengcf-npm-publish

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Legitimate Cloudflare team maintainer set on official scoped package. ai
bogus-package bogus-package AI (bogus-package): Popular official package; README/keyword heuristics are false positives. ai

Versions (showing 26 of 26)

Version Deps Published
0.8.2 0 / 8
0.8.1 0 / 8
0.8.0 0 / 8
0.7.2 0 / 8
0.7.1 0 / 8
0.7.0 0 / 8
0.6.0 0 / 8
0.5.0 0 / 8
0.4.0 0 / 8
0.3.3 0 / 8
0.3.2 0 / 8
0.3.1 0 / 8
0.3.0 0 / 8
0.2.4 0 / 8
0.2.3 0 / 8
0.2.2 0 / 9
0.1.0 0 / 9
0.0.13 0 / 9
0.0.12 0 / 9
0.0.11 0 / 9
0.0.10 0 / 9
0.0.9 0 / 9
0.0.8 0 / 9
0.0.7 0 / 8
0.0.6 0 / 8
0.0.5 1 / 4

v0.8.2

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.

v0.8.1

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.

v0.5.0

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.

v0.4.0

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.

v0.0.13

1 finding
LOW No provenance attestation provenance

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

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

2 findings
HIGH Publisher changed: cms1919 → threepointone (on 2025-08-07) provenance

This version was published by a different npm account than previous versions on 2025-08-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

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