AI company

Multi-agent team operating system for Claude Code. 108 MCP tools, 40+ agent templates, 10 lifecycle hooks, 7 pipeline workflows. Persistent teams, structured meetings, task wall, real-time React dashboard. No LangChain/AutoGen — pure CC native integration.

Agent Skills Python Listed MIT

Is AI company safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.4 / 10
Provenance None
Signed commits 0%
Last push today
Advisories None known
Compare AI company
Suggest a correction

In detail: AI company scores 59.3/100 (Grade C), ranked #114 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.4/10; recent commits are unsigned; no published advisory affects its latest release (ai-team-os); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How AI company 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 AI company and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Unsigned

    github.com/CronusL-1141/AI-company, MIT, last pushed 2026-10-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.4/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 4
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Linked, not attested

    • PyPI ai-team-os Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: ai-team-os 1.3.4. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-08 OSSF Scorecard: 3.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues AI company’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How AI company compares in Agent Skills

  1. #112 Claude Ads 59.4 +0.1
  2. #113 Claude Code Agent Monitor 59.3 ±0
  3. #114 AI company 59.3 this agent
  4. #115 Tech Leads Club Agent Skills 59.2 −0.1
  5. #116 Humanizer 59.2 −0.1

Bars show each HVTrust score; the tick marks AI company’s 59.3.

Where the 59.3 comes from

HVTrust dimensions vs the Agent Skills average

59.3 / 100 · 100.0% confidence

AI company Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.2 / 25
3.6 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.6 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
19.8 / 20
5.7 above avg 14.1
AdoptionLog-scaled stars · package downloads
7.4 / 20
1.6 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-10
Rank Moved
Rank rose 17 spots (#131 → #114)
2026-10-01
Rank Moved
Rank dropped 10 spots (#104 → #114)
2026-09-24
Rank Moved
Rank rose 10 spots (#109 → #99)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/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.
73.3
Activity sub-score · out of 100
#114

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-10 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
371
Forks
63
Last Push
2026-10-10
today
Commits (4 wk)
91
Downloads (7d)
8
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▲17
was #131

Analysis

Activity Inputs

73.3 / 100
StarsRepository reach
15.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
24.5 / 25
CommunityFork signal
8.4 / 20

Common questions about AI company

AI company 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 AI company publish package provenance?
No published build provenance is currently detected for AI company. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AI company have an OpenSSF Scorecard?
AI company has an OpenSSF Scorecard score of 3.4/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 AI company actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does AI company use?
AI company ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AI company's commits signed?
0% of the last 100 commits to AI company 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
AI company 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.
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
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to AI company's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain AI company?

For maintainers

HVTrust scores AI company 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
Rank 14Listed 2Score 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-10
Rank Moved
Rank rose 17 spots (#131 → #114)
2026-10-01
Rank Moved
Rank dropped 10 spots (#104 → #114)
2026-09-24
Rank Moved
Rank rose 10 spots (#109 → #99)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 169 spots (#278 → #109)
2026-09-23
HVTrust Changed
HVTrust up 29.4pts (29.2 → 58.6)
2026-09-22
Newly Listed
First tracked at rank #278
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Scorecard Added
OSSF Scorecard: 3.3/10
2026-09-08
Grade Changed
Trust grade D → C
2026-09-08
Rank Moved
Rank rose 198 spots (#294 → #96)
2026-09-08
HVTrust Changed
HVTrust up 25.6pts (32.8 → 58.4)
2026-09-08
Activity Score Changed
Activity score up 14pts (56 → 70)
2026-09-05
Rank Moved
Rank dropped 10 spots (#274 → #284)
2026-09-03
Rank Moved
Rank dropped 15 spots (#252 → #267)
2026-09-02
Rank Moved
Rank dropped 19 spots (#233 → #252)
2026-09-02
Activity Score Changed
Activity score down 7pts (66 → 59)
2026-09-01
Rank Moved
Rank dropped 12 spots (#221 → #233)
2026-08-31
Rank Moved
Rank dropped 17 spots (#204 → #221)
2026-08-30
Rank Moved
Rank dropped 35 spots (#169 → #204)
2026-08-29
Rank Moved
Rank dropped 41 spots (#128 → #169)
2026-08-28
Rank Moved
Rank dropped 27 spots (#101 → #128)
2026-08-27
Rank Moved
Rank dropped 23 spots (#78 → #101)
2026-08-26
Newly Listed
First tracked at rank #78

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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