Is Activepieces safe to use?

Activepieces has an HVTrust score of 40.3/100 (Grade D), ranked #594 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Activepieces?

Activepieces scores 40.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 23.7k GitHub stars and is categorized under Workflow Platforms.

Activepieces

activepieces/activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI W

Workflow Platforms TypeScript Grade D Listed NOASSERTION

40.3/100

Rank #594 of 1204

Compare Activepieces

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Tool Surface Changed +4

Is Activepieces safe? Activepieces scores 40.3/100 (Grade D), ranked #594 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#20 LiteFlow — 52.7 (C) → #21 PromptFlow — 42.5 (D) → #22 Superagent — 41.8 (D) → #24 ongrid — 23.3 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-09

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Redis

2026-08-08

Rank Moved

Rank dropped 193 spots (#385 → #578)

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.

Compare with another agent Get email alerts for Activepieces View Workflow Platforms Report missing data

93.0

Activity sub-score · out of 100

#23

In Workflow Platforms

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 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 →

Activity & Reach

Stars

23.7k

Forks

4.0k

Last Push

2026-08-09

today

Commits (4 wk)

337

Downloads (7d)

672,746

npm

HN mentions (30d)

—

Open Issues

366

Rank Change

▼16

was #578

Analysis

HVTrust Dimensions vs Workflow Platforms

40.3 / 100 · 67.0% confidence

Activepieces Workflow Platforms average (24 agents)

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

5.0 / 25

5.3 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.9 below avg 12.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

1.8 above avg 18.2

AdoptionLog-scaled stars · package downloads

18.3 / 20

5.5 above avg 12.8

Activity Inputs

93.0 / 100

StarsRepository reach

26.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

100%

of last 100 commits verified

Is Activepieces safe?

Public trust evidence for Activepieces 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 Activepieces publish package provenance?

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

Does Activepieces have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Activepieces. 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 Activepieces actively maintained?

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

What license does Activepieces use?

Activepieces ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Activepieces's commits signed?

100% of the last 100 commits to Activepieces 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 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.

browser
database

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

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 Activepieces'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-08-09

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Redis

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres, Redis

2026-07-17

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI

2026-07-17

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, OpenAI, Postgres, Redis

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Activepieces?

For maintainers

HVTrust scores Activepieces 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-08-09

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Redis

2026-08-08

Rank Moved

Rank dropped 193 spots (#385 → #578)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres, Redis

2026-07-29

Rank Moved

Rank dropped 10 spots (#365 → #375)

2026-07-17

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI

2026-07-17

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-07-15

Rank Moved

Rank dropped 25 spots (#333 → #358)

2026-07-14

Rank Moved

Rank dropped 17 spots (#316 → #333)

2026-07-13

Rank Moved

Rank dropped 35 spots (#281 → #316)

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock

2026-06-24

Rank Moved

Rank dropped 31 spots (#241 → #272)

2026-06-23

Rank Moved

Rank dropped 17 spots (#224 → #241)

2026-06-21

Rank Moved

Rank dropped 14 spots (#201 → #215)

2026-06-18

Rank Moved

Rank dropped 14 spots (#178 → #192)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, OpenAI, Postgres, Redis

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-02

Rank Moved

Rank dropped 11 spots (#153 → #164)

2026-06-01

Rank Moved

Rank dropped 17 spots (#136 → #153)

2026-05-29

HVTrust Changed

HVTrust up 6.6pts (31.3 → 37.9)

2026-05-27

HVTrust Changed

HVTrust down 13.0pts (62.3 → 49.3)

2026-05-24

Newly Listed

First tracked at rank #4

GitHub → npm: @activepieces/shared

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Workflow Platforms

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