Is llm-self-defense maintained?

GraphCanon rates llm-self-defense "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 805 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

Is llm-self-defense safe to use?

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

Is llm-self-defense a fork?

No. llm-self-defense is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does llm-self-defense have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 157 low - 157 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 llm-self-defense 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 llm-self-defense?

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

How does GraphCanon assess trust for llm-self-defense?

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/llm-self-defense/Trust report

Trust and health report

llm-self-defense - 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 · 26 views this month

Maintenance

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

Dormant18% signal

last push 805d ago

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 769276768
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: 157

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.9.3 · osv@v1

requirements.txt

GHSA-2vrm-gr82-f7m5

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-3wq7-rqq7-wx6j

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-4fvr-rgm6-gqmc

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-4m7w-qmgq-4wj5

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-54jq-c3m8-4m76

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-5m98-qgg9-wh84

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-63hf-3vf5-4wqf

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-63hw-fmq6-xxg2

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-69f9-5gxw-wvc2

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-6jhg-hg63-jvvf

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-6mq8-rvhq-8wgg

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-7gpw-8wmc-pm8g

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-8495-4g3g-x7pr

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-9548-qrrj-x5pj

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-966j-vmvw-g2g9

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-9x8q-7h8h-wcw9

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-c427-h43c-vf67

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-fh55-r93g-j68g

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-g3cq-j2xw-wf74

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-g84x-mcqj-x9qq

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-hcc4-c3v8-rx92

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-hg6j-4rv6-33pg

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-hpj7-wq8m-9hgp

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-jg22-mg44-37j8

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-jj3x-wxrx-4x23

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-m5qp-6w8w-w647

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-m6qw-4cw2-hm4m

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-mqqc-3gqh-h2x8

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-mwh4-6h8g-pg8w

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-p998-jp59-783m

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-w2fm-2cpv-w7v5

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-xcgm-r5h9-7989

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1097

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1098

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1099

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1100

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1101

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1102

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1103

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1104

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1105

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1106

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1107

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-1109

aiohttp@3.9.3 · osv@v1

requirements.txt

PYSEC-2026-237

aiohttp@3.9.3 · osv@v1

requirements.txt

GHSA-2qfp-q593-8484

Brotli@1.0.9 · osv@v1

requirements.txt

GHSA-248v-346w-9cwc

certifi@2024.2.2 · osv@v1

requirements.txt

PYSEC-2024-230

certifi@2024.2.2 · osv@v1

requirements.txt

GHSA-qmgc-5h2g-mvrw

filelock@3.13.1 · osv@v1

requirements.txt

GHSA-w853-jp5j-5j7f

filelock@3.13.1 · osv@v1

requirements.txt

PYSEC-2026-1374

filelock@3.13.1 · osv@v1

requirements.txt

PYSEC-2026-1375

filelock@3.13.1 · osv@v1

requirements.txt

GHSA-vqfr-h8mv-ghfj

h11@0.14.0 · osv@v1

requirements.txt

PYSEC-2026-348

h11@0.14.0 · osv@v1

requirements.txt

GHSA-65pc-fj4g-8rjx

idna@3.4 · osv@v1

requirements.txt

GHSA-jjg7-2v4v-x38h

idna@3.4 · osv@v1

requirements.txt

PYSEC-2024-60

idna@3.4 · osv@v1

requirements.txt

PYSEC-2026-215

idna@3.4 · osv@v1

requirements.txt

GHSA-cpwx-vrp4-4pq7

Jinja2@3.1.3 · osv@v1

requirements.txt

GHSA-gmj6-6f8f-6699

Jinja2@3.1.3 · osv@v1

requirements.txt

GHSA-h75v-3vvj-5mfj

Jinja2@3.1.3 · osv@v1

requirements.txt

GHSA-q2x7-8rv6-6q7h

Jinja2@3.1.3 · osv@v1

requirements.txt

PYSEC-2026-1471

Jinja2@3.1.3 · osv@v1

requirements.txt

PYSEC-2026-1472

Jinja2@3.1.3 · osv@v1

requirements.txt

PYSEC-2026-1474

Jinja2@3.1.3 · osv@v1

requirements.txt

PYSEC-2026-1475

Jinja2@3.1.3 · osv@v1

requirements.txt

GHSA-4xh5-x5gv-qwph

pip@23.3.1 · osv@v1

requirements.txt

GHSA-58qw-9mgm-455v

pip@23.3.1 · osv@v1

requirements.txt

GHSA-6vgw-5pg2-w6jp

pip@23.3.1 · osv@v1

requirements.txt

GHSA-jp4c-xjxw-mgf9

pip@23.3.1 · osv@v1

requirements.txt

GHSA-wf93-45jw-7689

pip@23.3.1 · osv@v1

requirements.txt

PYSEC-2026-1795

pip@23.3.1 · osv@v1

requirements.txt

PYSEC-2026-1796

pip@23.3.1 · osv@v1

requirements.txt

PYSEC-2026-196

pip@23.3.1 · osv@v1

requirements.txt

GHSA-7gcm-g887-7qv7

protobuf@3.20.3 · osv@v1

requirements.txt

GHSA-8qvm-5x2c-j2w7

protobuf@3.20.3 · osv@v1

requirements.txt

PYSEC-2026-1805

protobuf@3.20.3 · osv@v1

requirements.txt

PYSEC-2026-1806

protobuf@3.20.3 · osv@v1

requirements.txt

GHSA-5wvp-7f3h-6wmm

pyarrow@11.0.0 · osv@v1

requirements.txt

PYSEC-2023-238

pyarrow@11.0.0 · osv@v1

requirements.txt

PYSEC-2024-161

pyarrow@11.0.0 · osv@v1

requirements.txt

GHSA-9hjg-9r4m-mvj7

requests@2.31.0 · osv@v1

requirements.txt

GHSA-9wx4-h78v-vm56

requests@2.31.0 · osv@v1

requirements.txt

GHSA-gc5v-m9x4-r6x2

requests@2.31.0 · osv@v1

requirements.txt

PYSEC-2026-1872

requests@2.31.0 · osv@v1

requirements.txt

PYSEC-2026-1873

requests@2.31.0 · osv@v1

requirements.txt

GHSA-5rjg-fvgr-3xxf

setuptools@68.2.2 · osv@v1

requirements.txt

GHSA-cx63-2mw6-8hw5

setuptools@68.2.2 · osv@v1

requirements.txt

PYSEC-2025-49

setuptools@68.2.2 · osv@v1

requirements.txt

PYSEC-2026-1918

setuptools@68.2.2 · osv@v1

requirements.txt

GHSA-38vq-g6vr-w8wf

sentencepiece@0.1.99 · osv@v1

requirements.txt

PYSEC-2026-1909

sentencepiece@0.1.99 · osv@v1

requirements.txt

GHSA-63cw-57p8-fm3p

pytorch@2.2.0 · osv@v1

requirements.txt

PYSEC-2026-1856

pytorch@2.2.0 · osv@v1

requirements.txt

GHSA-g7vv-2v7x-gj9p

tqdm@4.65.0 · osv@v1

requirements.txt

PYSEC-2026-1976

tqdm@4.65.0 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-37q5-v5qm-c9v8

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-3863-2447-669p

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-6rvg-6v2m-4j46

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-fpwr-67px-3qhx

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-hxxf-235m-72v3

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-jjph-296x-mrcr

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-q2wp-rjmx-x6x9

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-qq3j-4f4f-9583

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-qxrp-vhvm-j765

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-v68g-wm8c-6x7j

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-wrfc-pvp9-mr9g

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2023-300

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2023-301

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2024-227

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2024-228

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2024-229

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2025-40

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1978

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1982

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1984

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1985

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1987

transformers@4.32.1 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.32.1 · osv@v1

requirements.txt

GHSA-2xpw-w6gg-jr37

urllib3@2.1.0 · osv@v1

requirements.txt

GHSA-34jh-p97f-mpxf

urllib3@2.1.0 · osv@v1

requirements.txt

GHSA-38jv-5279-wg99

urllib3@2.1.0 · osv@v1

requirements.txt

GHSA-gm62-xv2j-4w53

urllib3@2.1.0 · osv@v1

requirements.txt

GHSA-pq67-6m6q-mj2v

urllib3@2.1.0 · osv@v1

requirements.txt

GHSA-qccp-gfcp-xxvc

urllib3@2.1.0 · osv@v1

requirements.txt

PYSEC-2026-141

urllib3@2.1.0 · osv@v1

requirements.txt

PYSEC-2026-1994

urllib3@2.1.0 · osv@v1

requirements.txt

PYSEC-2026-1995

urllib3@2.1.0 · osv@v1

requirements.txt

PYSEC-2026-1996

urllib3@2.1.0 · osv@v1

requirements.txt

PYSEC-2026-1998

urllib3@2.1.0 · osv@v1

requirements.txt

PYSEC-2026-1999

urllib3@2.1.0 · osv@v1

requirements.txt

GHSA-8rrh-rw8j-w5fx

wheel@0.41.2 · osv@v1

requirements.txt

PYSEC-2026-2047

wheel@0.41.2 · osv@v1

requirements.txt

GHSA-jfmj-5v4g-7637

zipp@3.17.0 · osv@v1

requirements.txt

PYSEC-2026-2074

zipp@3.17.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/poloclub-llm-self-defense/trust.

Common questions

Is llm-self-defense maintained?: GraphCanon rates llm-self-defense "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 805 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is llm-self-defense safe to use?: Last scanned 1mo (deps profile). Status: 157 low - 157 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 llm-self-defense as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is llm-self-defense a fork?: No. llm-self-defense is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does llm-self-defense have known security vulnerabilities?: Last scanned 1mo (deps profile). Status: 157 low - 157 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 llm-self-defense 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 llm-self-defense?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for llm-self-defense. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for llm-self-defense?: 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.