---
title: "ChatGPT-On-CS trust report"
type: "trust-report"
slug: "cs-lazy-tools-chatgpt-on-cs"
canonical_url: "https://www.graphcanon.com/tools/cs-lazy-tools-chatgpt-on-cs/trust"
computed_at: "2026-07-15T10:54:24.548Z"
maintenance_label: "Steady"
security_status: "no_lockfile"
---

# ChatGPT-On-CS trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and external security intelligence providers. Not a security guarantee._

## Maintenance

- Label: Steady (60% recency signal)
- Days since last push: 39
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 768534013
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-15T10:54:24.548Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: No lockfile (source not queried)
  - Last query: 2026-07-15T10:54:25.503761+00:00
  - Evidence: https://osv.dev/
- **deps.dev advisories**: Not queried
  - Evidence: https://deps.dev/
- **OpenSSF Scorecard**: Not queried
  - Evidence: https://api.securityscorecards.dev/projects/github.com/cs-lazy-tools/ChatGPT-On-CS
  - Note: Weekly public scans omit some checks at scale.

## Method and caveats

These are heuristics from public GitHub data and external security intelligence providers, sourced and dated. 
"No published findings from this source" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is ChatGPT-On-CS maintained?

GraphCanon rates ChatGPT-On-CS "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 39 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is ChatGPT-On-CS safe to use?

Last scanned today (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits. GraphCanon does not certify ChatGPT-On-CS as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is ChatGPT-On-CS a fork?

No. ChatGPT-On-CS is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does ChatGPT-On-CS have known security vulnerabilities?

Last scanned today (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits.

### How often is the ChatGPT-On-CS 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 ChatGPT-On-CS?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for ChatGPT-On-CS. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for ChatGPT-On-CS?

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](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/cs-lazy-tools-chatgpt-on-cs/trust`](/api/graphcanon/tools/cs-lazy-tools-chatgpt-on-cs/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_