crawlab-team/crawlab · Security & risks

Authoritative risk signals for crawlab-team/crawlab — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

Architecture Security & risks Dependencies License Maintenance Alternatives Vs Full analysis

Dependency CVEs (deps.dev)

Critical

0 direct

High

0 direct

Moderate

Deps scanned

6 direct

GO-2022-0635 · github.com/aws/aws-sdk-goIn-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-goMODERATE
GO-2022-0646 · github.com/aws/aws-sdk-goCBC padding oracle issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-goMODERATE

OpenSSF Scorecard · 3.9/10

Signed-Releases—
Branch-Protection—
Maintained0/10
Code-Review0/10
CII-Best-Practices0/10
Token-Permissions0/10
Fuzzing0/10
SAST0/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about crawlab-team/crawlab

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.