# io.github.CloudCorpRecords/actionpin (npm · @reneturcios/actionpin)

GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `@reneturcios/actionpin`: 72/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-actionpin/reneturcios-actionpin.md), [page](https://verifymcp.io/servers/cloudcorprecords-actionpin/reneturcios-actionpin)
- oci · `ghcr.io/cloudcorprecords/actionpin`: 48/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-actionpin/ghcr-io-cloudcorprecords-actionpin.md), [page](https://verifymcp.io/servers/cloudcorprecords-actionpin/ghcr-io-cloudcorprecords-actionpin)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/actionpin`
- Version: `0.1.8`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 302 tokens (~100/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/actionpin MCP server?

io.github.CloudCorpRecords/actionpin runs locally as an npm package, launched with npx -y @reneturcios/actionpin. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-actionpin -- npx -y @reneturcios/actionpin
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-actionpin": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/actionpin"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-actionpin": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/actionpin"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-actionpin -- npx -y @reneturcios/actionpin
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-actionpin": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/actionpin"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-actionpin --command npx --arg -y --arg @reneturcios/actionpin
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-actionpin:
    command: "npx"
    args: ["-y", "@reneturcios/actionpin"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-actionpin": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/actionpin"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-actionpin -t stdio -c npx -a -y @reneturcios/actionpin
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-actionpin": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/actionpin"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 53, −14)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 206 → 302
- [functional] Package version: 0.1.7 → 0.1.8

### 2026-10-24 (score 67, +11)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail
- [security improvement] Malware scan: unverified → pass

### 2026-10-23 (score 56, −4)

- [security regression] Malware scan: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85
- [functional] Package version: 0.1.6 → 0.1.7

## MCP tools (3)

### `audit_workflows` (~115 tokens)

Audit GitHub workflow files under a repo path for action pinning. Finds every uses: reference, classifies it as PINNED (full 40-char SHA), MUTABLE (version tag), BRANCH, or LOCAL, labels the owner as official, third-party, docker, or local, and returns a PINNED, EXPOSED, or PARTIAL verdict with the file and line for every action.

Input parameters:

- `path` (string, required): Repo root, a .github/workflows directory, or a single workflow file

### `audit_org` (~96 tokens)

Audit every repo under an org root (each immediate subdirectory that carries workflows is one repo) and report pin drift across the org: every action that is used at different refs in different repos, naming each ref and the repos that use it. The org verdict is the worst per-repo verdict; drift itself does not change the verdict.

Input parameters:

- `path` (string, required): Org root: a directory whose immediate subdirectories are repo checkouts

### `pin_plan` (~91 tokens)

Build the SHA pinning plan for workflows under a repo path without writing any files. Resolves each mutable or branch ref to a commit SHA through the GitHub API and returns the exact rewritten line per action, or a failed entry with the reason when resolution is not possible. Local refs are never rewritten.

Input parameters:

- `path` (string, required): Repo root, a .github/workflows directory, or a single workflow file

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-actionpin/reneturcios-actionpin#diagnostics

## Score history

- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 53
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 56
- 2026-10-22: 60

## Common questions

### What is the io.github.CloudCorpRecords/actionpin MCP server?

io.github.CloudCorpRecords/actionpin is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/actionpin. GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan. This page covers its npm package (@reneturcios/actionpin).

### Is the io.github.CloudCorpRecords/actionpin MCP server safe to use?

io.github.CloudCorpRecords/actionpin scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/actionpin MCP server expose?

io.github.CloudCorpRecords/actionpin exposes 3 tools: audit_workflows, audit_org, pin_plan. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/actionpin MCP server still maintained?

io.github.CloudCorpRecords/actionpin is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/actionpin MCP server under?

io.github.CloudCorpRecords/actionpin declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/actionpin
- Socket report: https://socket.dev/npm/package/@reneturcios/actionpin
- Repository: https://github.com/CloudCorpRecords/actionpin
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-actionpin/reneturcios-actionpin.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-actionpin/reneturcios-actionpin.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-actionpin/reneturcios-actionpin