Is whisper-writer maintained?

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

Is whisper-writer safe to use?

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

Is whisper-writer a fork?

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

Does whisper-writer have known security vulnerabilities?

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

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

What does GraphCanon never claim about whisper-writer?

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

How does GraphCanon assess trust for whisper-writer?

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/whisper-writer/Trust report

Trust and health report

whisper-writer - trust report

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

GraphCanon updated 3w · GitHub synced 3w

Maintenance

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

Dormant18% signal

last push 705d ago · last release 2y

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 629730614
Not a fork
Personal account
Computed 3w

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: 123

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

requirements.txt

GHSA-2vrm-gr82-f7m5

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-3wq7-rqq7-wx6j

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-45c4-8wx5-qw6w

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-4fvr-rgm6-gqmc

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-4m7w-qmgq-4wj5

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-54jq-c3m8-4m76

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-5h86-8mv2-jq9f

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-5m98-qgg9-wh84

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-63hf-3vf5-4wqf

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-63hw-fmq6-xxg2

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-69f9-5gxw-wvc2

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-6jhg-hg63-jvvf

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-6mq8-rvhq-8wgg

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-7gpw-8wmc-pm8g

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-8495-4g3g-x7pr

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-8qpw-xqxj-h4r2

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-9548-qrrj-x5pj

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-966j-vmvw-g2g9

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-9x8q-7h8h-wcw9

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-c427-h43c-vf67

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-fh55-r93g-j68g

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-g3cq-j2xw-wf74

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-g84x-mcqj-x9qq

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-gfw2-4jvh-wgfg

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-hcc4-c3v8-rx92

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-hg6j-4rv6-33pg

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-hpj7-wq8m-9hgp

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-jg22-mg44-37j8

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-jj3x-wxrx-4x23

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-m5qp-6w8w-w647

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-m6qw-4cw2-hm4m

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-mqqc-3gqh-h2x8

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-mwh4-6h8g-pg8w

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-p998-jp59-783m

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-pjjw-qhg8-p2p9

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-q3qx-c6g2-7pw2

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-qvrw-v9rv-5rjx

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-w2fm-2cpv-w7v5

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-xcgm-r5h9-7989

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2023-120

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2023-246

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2023-250

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2023-251

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2024-24

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2024-26

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1097

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1098

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1099

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1100

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1101

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1102

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1103

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1104

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1105

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1106

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1107

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-1109

aiohttp@3.8.4 · osv@v1

requirements.txt

PYSEC-2026-237

aiohttp@3.8.4 · osv@v1

requirements.txt

GHSA-248v-346w-9cwc

certifi@2023.5.7 · osv@v1

requirements.txt

GHSA-xqr8-7jwr-rhp7

certifi@2023.5.7 · osv@v1

requirements.txt

PYSEC-2023-135

certifi@2023.5.7 · osv@v1

requirements.txt

PYSEC-2024-230

certifi@2023.5.7 · osv@v1

requirements.txt

GHSA-qmgc-5h2g-mvrw

filelock@3.12.0 · osv@v1

requirements.txt

GHSA-w853-jp5j-5j7f

filelock@3.12.0 · osv@v1

requirements.txt

PYSEC-2026-1374

filelock@3.12.0 · osv@v1

requirements.txt

PYSEC-2026-1375

filelock@3.12.0 · 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.2 · osv@v1

requirements.txt

GHSA-gmj6-6f8f-6699

Jinja2@3.1.2 · osv@v1

requirements.txt

GHSA-h5c8-rqwp-cp95

Jinja2@3.1.2 · osv@v1

requirements.txt

GHSA-h75v-3vvj-5mfj

Jinja2@3.1.2 · osv@v1

requirements.txt

GHSA-q2x7-8rv6-6q7h

Jinja2@3.1.2 · osv@v1

requirements.txt

PYSEC-2026-1471

Jinja2@3.1.2 · osv@v1

requirements.txt

PYSEC-2026-1472

Jinja2@3.1.2 · osv@v1

requirements.txt

PYSEC-2026-1473

Jinja2@3.1.2 · osv@v1

requirements.txt

PYSEC-2026-1474

Jinja2@3.1.2 · osv@v1

requirements.txt

PYSEC-2026-1475

Jinja2@3.1.2 · osv@v1

requirements.txt

GHSA-3f63-hfp8-52jq

Pillow@9.5.0 · osv@v1

requirements.txt

GHSA-44wm-f244-xhp3

Pillow@9.5.0 · osv@v1

requirements.txt

GHSA-8ghj-p4vj-mr35

Pillow@9.5.0 · osv@v1

requirements.txt

GHSA-j7hp-h8jx-5ppr

Pillow@9.5.0 · osv@v1

requirements.txt

GHSA-r73j-pqj5-w3x7

Pillow@9.5.0 · osv@v1

requirements.txt

GHSA-wjx4-4jcj-g98j

Pillow@9.5.0 · osv@v1

requirements.txt

PYSEC-2023-175

Pillow@9.5.0 · osv@v1

requirements.txt

PYSEC-2023-227

Pillow@9.5.0 · osv@v1

requirements.txt

PYSEC-2026-165

Pillow@9.5.0 · osv@v1

requirements.txt

PYSEC-2026-1793

Pillow@9.5.0 · osv@v1

requirements.txt

PYSEC-2026-1794

Pillow@9.5.0 · osv@v1

requirements.txt

PYSEC-2026-457

Pillow@9.5.0 · osv@v1

requirements.txt

GHSA-7gcm-g887-7qv7

protobuf@4.25.1 · osv@v1

requirements.txt

GHSA-8qvm-5x2c-j2w7

protobuf@4.25.1 · osv@v1

requirements.txt

PYSEC-2026-1805

protobuf@4.25.1 · osv@v1

requirements.txt

PYSEC-2026-1806

protobuf@4.25.1 · osv@v1

requirements.txt

GHSA-mf9w-mj56-hr94

python-dotenv@1.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-g7vv-2v7x-gj9p

tqdm@4.65.0 · osv@v1

requirements.txt

PYSEC-2026-1976

tqdm@4.65.0 · osv@v1

requirements.txt

GHSA-2xpw-w6gg-jr37

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-34jh-p97f-mpxf

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-38jv-5279-wg99

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-g4mx-q9vg-27p4

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-gm62-xv2j-4w53

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-pq67-6m6q-mj2v

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-qccp-gfcp-xxvc

urllib3@2.0.2 · osv@v1

requirements.txt

GHSA-v845-jxx5-vc9f

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2023-192

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2023-212

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2026-141

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2026-1994

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2026-1995

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2026-1996

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2026-1998

urllib3@2.0.2 · osv@v1

requirements.txt

PYSEC-2026-1999

urllib3@2.0.2 · 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/savbell-whisper-writer/trust.

Common questions

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