Comp AI CRM

Comp AI CRM is an open source, CRM designed for AI agents. Agentic-first CRM.

Research & Data TypeScript Listed MIT

Is Comp AI CRM safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 93%
Last push 22d ago
Compare Comp AI CRM
Suggest a correction

In detail: Comp AI CRM scores 19.8/100 (Grade D), ranked #1343 of 1346 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 93% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Comp AI CRM 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.

Chain of custody

Scanners check what the code says. This traces who ships Comp AI CRM and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run.

  1. Source Signed

    github.com/trycompai/crm, MIT, last pushed 2026-09-11. 93% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages None

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

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Comp AI CRM.

Evidence behind this score

Coverage D: 1 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Comp AI CRM’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.

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 Comp AI CRM compares in Research & Data

  1. #32 Agent Laboratory 23.0 +3.2
  2. #33 DeepAnalyze 22.1 +2.3
  3. #34 Comp AI CRM 19.8 this agent
  4. #35 ai-hedge-fund-crypto 16.2 −3.6
  5. #36 InternAgent 14.3 −5.5

Bars show each HVTrust score; the tick marks Comp AI CRM’s 19.8.

Where the 19.8 comes from

HVTrust dimensions vs the Research & Data average

19.8 / 100 · 50.0% confidence

Comp AI CRM Research & Data average (36 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.7 / 25
3.3 below avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.1 below avg 11.6
Maintenance60% last-push freshness · 40% commit activity
10.5 / 20
2.7 below avg 13.2
AdoptionLog-scaled stars · package downloads
9.7 / 20
1.1 below avg 10.8

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-10-01
Newly Listed
First tracked at rank #1343
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
61.1
Activity sub-score · out of 100
#34

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

Signals refreshed 2026-10-03 16:08 UTC · Repo last pushed 22 days ago

Rank Trend

2026-10-01 2026-10-03

Activity & Reach

Stars
11.0k
Forks
1.6k
Last Push
2026-09-11
22 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
17
Rank Change
=
was #1343

Analysis

Activity Inputs

61.1 / 100
StarsRepository reach
24.3 / 30
FreshnessLast push recency
21.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.9 / 20

Common questions about Comp AI CRM

Public trust evidence for Comp AI CRM is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Comp AI CRM publish package provenance?
No published build provenance is currently detected for Comp AI CRM. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Comp AI CRM have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Comp AI CRM. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Comp AI CRM actively maintained?
Maintained. Last push was 22 days ago.
What license does Comp AI CRM use?
Comp AI CRM ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Comp AI CRM's commits signed?
93% of the last 100 commits to Comp AI CRM 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
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 Comp AI CRM?

For maintainers

HVTrust scores Comp AI CRM 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.

Reputation Timeline

Signal history
Listed 1
2026-10-01
Newly Listed
First tracked at rank #1343

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 19.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/comp-ai-crm.svg)](https://hvtracker.net/agents/comp-ai-crm)
HTML:
<a href="https://hvtracker.net/agents/comp-ai-crm"><img src="https://hvtracker.net/badge/comp-ai-crm.svg" alt="HVTrust"></a>

Other agents in Research & Data

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