Is Chat on Steroids safe to use?

Chat on Steroids has an HVTrust score of 63.2/100 (Grade C), ranked #607 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Chat on Steroids?

Chat on Steroids scores 63.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 5.2k GitHub stars and is categorized under MCP Servers.

Chat on Steroids

Repository

Cross-platform local MCP capabilities for ChatGPT with Chrome integration, Goal, Compact & Resume, and durable multi-agent workflows.

MCP Servers TypeScript Listed MIT

Is Chat on Steroids safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.7 / 10

Provenance None

Signed commits 29%

Last push yesterday

Compare Chat on Steroids

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Chat on Steroids scores 63.2/100 (Grade C), ranked #607 of 1387 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.7/10; 29% of recent commits are signed; last pushed 2026-11-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Chat on Steroids could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.7 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +6.9 → 70.1 B · #226 of 779
Sign every commit29% signed today +3.5 → 66.7 B · #276 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Chat on Steroids and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/totec448-spec/chat-on-steroids, MIT, last pushed 2026-11-14. 29% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.7/10 (scanned Nov 12, 2026). The checks that decide who can get a change released:
- Code Review7
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies9
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 9

SAST 10

Security-Policy 4

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 0
Published packages None

No registry package. Chat on Steroids is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-10-13 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Chat on Steroids’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Chat on Steroids compares in MCP Servers

#338 Studio MCP 63.3 +0.1
#339 Paparats – Local Semantic Code Search MCP 63.3 +0.1
#340 Chat on Steroids 63.2 this agent
#341 Korean Law MCP 63.0 −0.2
#342 Hackmd MCP 63.0 −0.2

Bars show each HVTrust score; the tick marks Chat on Steroids’s 63.2.

Where the 63.2 comes from

HVTrust dimensions vs the MCP Servers average

63.2 / 100 · 100.0% confidence

Chat on Steroids MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.6 / 25

2.3 below avg 10.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.0 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

8.9 / 20

1.3 above avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-12

Rank Moved

Rank rose 32 spots (#629 → #597)

2026-11-07

Rank Moved

Rank rose 17 spots (#648 → #631)

2026-10-25

Rank Moved

Rank dropped 28 spots (#603 → #631)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

85.5

Activity sub-score · out of 100

#340

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars

5.2k

Forks

675

Last Push

2026-11-14

yesterday

Commits (4 wk)

2244

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #605

Analysis

Activity Inputs

85.5 / 100

StarsRepository reach

22.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

13.2 / 20

Common questions about Chat on Steroids

Chat on Steroids has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Chat on Steroids publish package provenance?

No published build provenance is currently detected for Chat on Steroids. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Chat on Steroids have an OpenSSF Scorecard?

Chat on Steroids has an OpenSSF Scorecard score of 5.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Chat on Steroids actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Chat on Steroids use?

Chat on Steroids ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Chat on Steroids's commits signed?

28% of the last 100 commits to Chat on Steroids are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Chat on Steroids appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Chat on Steroids?

For maintainers

HVTrust scores Chat on Steroids from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-12

Rank Moved

Rank rose 32 spots (#629 → #597)

2026-11-07

Rank Moved

Rank rose 17 spots (#648 → #631)

2026-10-25

Rank Moved

Rank dropped 28 spots (#603 → #631)

2026-10-23

Rank Moved

Rank dropped 18 spots (#586 → #604)

2026-10-21

Rank Moved

Rank dropped 13 spots (#575 → #588)

2026-10-20

Rank Moved

Rank rose 11 spots (#586 → #575)

2026-10-14

Rank Moved

Rank dropped 15 spots (#555 → #570)

2026-10-13

Scorecard Added

OSSF Scorecard: 5.7/10

2026-10-13

Grade Changed

Trust grade D → C

2026-10-13

Rank Moved

Rank rose 792 spots (#1347 → #555)

2026-10-13

HVTrust Changed

HVTrust up 37.1pts (26.7 → 63.8)

2026-10-09

Rank Moved

Rank dropped 13 spots (#1323 → #1336)

2026-09-29

Newly Listed

First tracked at rank #1317

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/chat-on-steroids.svg)](https://hvtracker.net/agents/chat-on-steroids)
            
HTML:
            <a href="https://hvtracker.net/agents/chat-on-steroids"><img src="https://hvtracker.net/badge/chat-on-steroids.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Chat on Steroids

How Chat on Steroids could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Chat on Steroids compares in MCP Servers

Where the 63.2 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Chat on Steroids

AI agent surface

Maintain Chat on Steroids?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers