Is continuum maintained?

GraphCanon rates continuum "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 2 days ago. 5 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Is continuum safe to use?

Last scanned today (deps profile). Status: 68 low - 68 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify continuum as safe - review maintenance, provenance, and scan findings on this page before adopting.

No. continuum is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does continuum have known security vulnerabilities?

Last scanned today (deps profile). Status: 68 low - 68 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

How often is the continuum trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).

What does GraphCanon never claim about continuum?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for continuum. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for continuum?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/continuum/Trust report

Trust and health report

continuum - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated today · GitHub synced today

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 2d ago · last release 1w · 5 releases (90d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 1250579815
Not a fork
Verified publisher: organization account
Computed today

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

Published findings

Last query: today
Scanner: osv@v1
Stored findings: 68

View source evidence

deps.dev advisories

Not queried

Scanner: deps.dev@v1

View source evidence

OpenSSF Scorecard

Not queried

Scanner: openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-2fqr-mr3j-6wp8

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-2vrm-gr82-f7m5

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-3wq7-rqq7-wx6j

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-4fvr-rgm6-gqmc

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-4m7w-qmgq-4wj5

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-54jq-c3m8-4m76

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-63hf-3vf5-4wqf

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-63hw-fmq6-xxg2

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-69f9-5gxw-wvc2

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-6jhg-hg63-jvvf

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-6mq8-rvhq-8wgg

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-966j-vmvw-g2g9

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-9x8q-7h8h-wcw9

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-c427-h43c-vf67

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-fh55-r93g-j68g

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-g3cq-j2xw-wf74

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-g84x-mcqj-x9qq

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-hcc4-c3v8-rx92

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-hg6j-4rv6-33pg

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-hpj7-wq8m-9hgp

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-jg22-mg44-37j8

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-jj3x-wxrx-4x23

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-m5qp-6w8w-w647

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-m6qw-4cw2-hm4m

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-mqqc-3gqh-h2x8

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-mwh4-6h8g-pg8w

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-p998-jp59-783m

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-w2fm-2cpv-w7v5

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-xcgm-r5h9-7989

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1097

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1099

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1100

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1101

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1105

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1106

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1107

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-1109

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2094

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2095

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2096

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2097

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2098

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2099

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2100

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2101

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2102

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2103

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2104

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2105

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2106

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2107

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2108

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2109

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2110

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2111

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2112

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-2113

aiohttp@3.13.2 · osv@v1

requirements.txt

PYSEC-2026-237

aiohttp@3.13.2 · osv@v1

requirements.txt

GHSA-mf9w-mj56-hr94

python-dotenv@1.0.1 · osv@v1

requirements.txt

PYSEC-2026-2270

python-dotenv@1.0.1 · osv@v1

requirements.txt

GHSA-cgx8-qgvr-f7vf

mem0ai@1.0.0 · osv@v1

requirements.txt

GHSA-gq6f-qwv9-rf4j

mem0ai@1.0.0 · osv@v1

requirements.txt

GHSA-jfv9-68m5-gjjr

mem0ai@1.0.0 · osv@v1

requirements.txt

GHSA-xqxw-r767-67m7

mem0ai@1.0.0 · osv@v1

requirements.txt

PYSEC-2026-2633

mem0ai@1.0.0 · osv@v1

requirements.txt

PYSEC-2026-2634

mem0ai@1.0.0 · osv@v1

requirements.txt

PYSEC-2026-2635

mem0ai@1.0.0 · osv@v1

requirements.txt

PYSEC-2026-2636

mem0ai@1.0.0 · osv@v1

requirements.txt

Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/shyftlabs-continuum/trust.

Common questions

Is continuum maintained?: GraphCanon rates continuum "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 2 days ago. 5 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is continuum safe to use?: Last scanned today (deps profile). Status: 68 low - 68 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify continuum as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is continuum a fork?: No. continuum is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does continuum have known security vulnerabilities?: Last scanned today (deps profile). Status: 68 low - 68 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the continuum trust report updated?: Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).
What does GraphCanon never claim about continuum?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for continuum. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for continuum?: Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.