Is coder_reviewer_reranking maintained?

coder_reviewer_reranking is archived on GitHub. GraphCanon treats archived repositories as dormant regardless of past activity.

Is coder_reviewer_reranking safe to use?

Last scanned 1mo (deps profile). Status: 85 low - 85 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 coder_reviewer_reranking as safe - review maintenance, provenance, and scan findings on this page before adopting.

Is coder_reviewer_reranking a fork?

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

Does coder_reviewer_reranking have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 85 low - 85 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 coder_reviewer_reranking trust report updated?

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

What does GraphCanon never claim about coder_reviewer_reranking?

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

How does GraphCanon assess trust for coder_reviewer_reranking?

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/coder_reviewer_reranking/Trust report

Trust and health report

coder_reviewer_reranking - trust report

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

GraphCanon updated 2w · GitHub synced 2w

Maintenance

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

Archived8% signal

last push 1267d ago

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 571849314
Not a fork
Verified publisher: organization account
Computed 2w

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: 1mo
Scanner: osv@v1
Stored findings: 85

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-qmgc-5h2g-mvrw

filelock@3.7.1 · osv@v1

requirements.txt

GHSA-w853-jp5j-5j7f

filelock@3.7.1 · osv@v1

requirements.txt

PYSEC-2026-1374

filelock@3.7.1 · osv@v1

requirements.txt

PYSEC-2026-1375

filelock@3.7.1 · osv@v1

requirements.txt

GHSA-469j-vmhf-r6v7

nltk@3.7 · osv@v1

requirements.txt

GHSA-68j8-pq59-fqgm

nltk@3.7 · osv@v1

requirements.txt

GHSA-7p94-766c-hgjp

nltk@3.7 · osv@v1

requirements.txt

GHSA-cgvx-9447-vcch

nltk@3.7 · osv@v1

requirements.txt

GHSA-gfwx-w7gr-fvh7

nltk@3.7 · osv@v1

requirements.txt

GHSA-h8wq-7xc4-p3qx

nltk@3.7 · osv@v1

requirements.txt

GHSA-jm6w-m3j8-898g

nltk@3.7 · osv@v1

requirements.txt

GHSA-p4gq-832x-fm9v

nltk@3.7 · osv@v1

requirements.txt

GHSA-rf74-v2fm-23pw

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2024-167

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-2078

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-2085

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-597

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-96

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-97

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-98

nltk@3.7 · osv@v1

requirements.txt

PYSEC-2026-99

nltk@3.7 · osv@v1

requirements.txt

GHSA-3f63-hfp8-52jq

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-44wm-f244-xhp3

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-8ghj-p4vj-mr35

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-j7hp-h8jx-5ppr

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-q4mp-jvh2-76fj

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-r73j-pqj5-w3x7

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-wjx4-4jcj-g98j

Pillow@9.2.0 · osv@v1

requirements.txt

OSV-2022-1074

Pillow@9.2.0 · osv@v1

requirements.txt

OSV-2022-715

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2022-42980

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2023-175

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2023-227

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2026-165

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2026-1793

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2026-1794

Pillow@9.2.0 · osv@v1

requirements.txt

PYSEC-2026-457

Pillow@9.2.0 · osv@v1

requirements.txt

GHSA-g7vv-2v7x-gj9p

tqdm@4.64.1 · osv@v1

requirements.txt

PYSEC-2026-1976

tqdm@4.64.1 · osv@v1

requirements.txt

GHSA-282v-666c-3fvg

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-37q5-v5qm-c9v8

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-3863-2447-669p

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-6rvg-6v2m-4j46

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-fpwr-67px-3qhx

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-hxxf-235m-72v3

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-jjph-296x-mrcr

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-q2wp-rjmx-x6x9

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-qq3j-4f4f-9583

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-qxrp-vhvm-j765

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-v68g-wm8c-6x7j

transformers@4.23.1 · osv@v1

requirements.txt

GHSA-wrfc-pvp9-mr9g

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2023-299

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2023-300

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2023-301

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2024-227

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2024-228

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2024-229

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2025-40

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1978

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1982

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1984

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1985

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1987

transformers@4.23.1 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.23.1 · 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/facebookresearch-coder-reviewer-reranking/trust.

Common questions

Is coder_reviewer_reranking maintained?: coder_reviewer_reranking is archived on GitHub. GraphCanon treats archived repositories as dormant regardless of past activity.
Is coder_reviewer_reranking safe to use?: Last scanned 1mo (deps profile). Status: 85 low - 85 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 coder_reviewer_reranking as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is coder_reviewer_reranking a fork?: No. coder_reviewer_reranking is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does coder_reviewer_reranking have known security vulnerabilities?: Last scanned 1mo (deps profile). Status: 85 low - 85 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 coder_reviewer_reranking trust report updated?: Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
What does GraphCanon never claim about coder_reviewer_reranking?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for coder_reviewer_reranking. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for coder_reviewer_reranking?: 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.