@pydantic/logfire-cf-workers
Cloudflare workers integration for Logfire - https://pydantic.dev/logfire
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pydantic/logfire-api | AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Pydantic org package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this package. | ai | |
| dependencies | unvetted-dep:@pydantic/otel-cf-workers | AI (dependencies): Sibling package under the same @pydantic org; same publisher and repo context. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 2 / 4 | |
| 2.0.3 | 2 / 4 | |
| 2.0.2 | 2 / 4 | |
| 2.0.1 | 2 / 4 | |
| 2.0.0 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.12.4 | 2 / 4 | |
| 0.12.3 | 2 / 4 | |
| 0.12.2 | 2 / 4 | |
| 0.12.1 | 2 / 4 | |
| 0.12.0 | 2 / 4 | |
| 0.11.11 | 2 / 4 | |
| 0.11.10 | 2 / 4 | |
| 0.11.9 | 2 / 4 | |
| 0.11.8 | 2 / 4 | |
| 0.11.7 | 2 / 4 | |
| 0.11.6 | 2 / 4 | |
| 0.11.5 | 2 / 4 | |
| 0.11.4 | 2 / 4 | |
| 0.11.3 | 2 / 4 | |
| 0.11.2 | 2 / 4 | |
| 0.11.1 | 2 / 11 | |
| 0.11.0 | 2 / 9 | |
| 0.10.0 | 2 / 9 | |
| 0.9.0 | 2 / 9 | |
| 0.8.2 | 2 / 9 | |
| 0.8.1 | 2 / 9 | |
| 0.8.0 | 2 / 9 | |
| 0.7.0 | 2 / 9 | |
| 0.6.0 | 2 / 9 | |
| 0.5.0 | 2 / 9 | |
| 0.4.4 | 2 / 9 | |
| 0.4.3 | 2 / 9 | |
| 0.4.2 | 2 / 9 | |
| 0.4.1 | 2 / 9 | |
| 0.4.0 | 2 / 9 | |
| 0.3.0 | 2 / 9 | |
| 0.2.2 | 1 / 9 | |
| 0.2.1 | 0 / 10 |
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.