Closed kylewillmon closed 11 months ago
The analysis contains 2 package(s) Phylum has not yet processed, preventing a complete risk analysis. Phylum is processing these packages currently and should complete soon. Please wait for up to 30 minutes, then re-run the analysis.
Looks like the build requires protoc
now, which is causing CI to fail....
I'll investigate later today to see if I can avoid the dependency
It looks like there is no opt out. protoc
has been required to build deno since denoland/deno@2d9298f
I'll update the workflows to restore CI.
The Phylum risk analysis is complete and has passed the active policy.
The analysis contains 1 package(s) Phylum has not yet processed, preventing a complete risk analysis. Phylum is processing these packages currently and should complete soon. Please wait for up to 30 minutes, then re-run the analysis.
I've opened littledivy/aead-gcm-stream#2 to fix the build error on Rust 1.71.0
Hoping to get a quick response there. I'd rather not bump MSRV beyond the latest 3 minor releases.
This repository analyzes the risk of new dependencies. An administrator of this repository has set requirements via Phylum policy.
If you see this comment, one or more dependencies have failed Phylum's risk analysis.
rsa@0.9.3
failed.Risk Domain: Software Vulnerability
Risk Level: high
Reason: risk level cannot exceed medium
Risk Domain: Software Vulnerability
Risk Level: high
Reason: risk level cannot exceed medium
This repository analyzes the risk of new dependencies. An administrator of this repository has set requirements via Phylum policy.
If you see this comment, one or more dependencies have failed Phylum's risk analysis.
rsa@0.9.5
failed.Risk Domain: Software Vulnerability
Risk Level: high
Reason: risk level cannot exceed medium
Risk Domain: Software Vulnerability
Risk Level: high
Reason: risk level cannot exceed medium
The Phylum risk analysis is complete and has passed the active policy.
This includes migration to the new
op2
macro becauseop
is now deprecated (See denoland/deno_core#279). The new macro requires explicit annotation for string and serde parameters and return values because of the performance hit. We use these heavily (and don't care about the performance).