← Home

@airtable/mcp-cli

Airtable MCP CLI — auto-discovers commands from the MCP server

4
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

airtabledougairtable_ops_team_productiondjmally-airtablerichsinns2tephensyrnickadarlieberdembokevinwilde-atclementhoang-atwillpowelsonatblakethomson-atnabeelairtablelarsj-atcarolinekimatit.opsanshul2203jbuzaid-airtableboyang.sunduretti-atjonathan.xiepatrickliu-atderekwu-at

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publishing backed by SLSA provenance attestation; consistent with official Airtable org automation. ai
source-diff net-exec-file:dist/bin.js AI (source-diff): Standard esbuild bundle of MCP CLI; network calls are MCP SDK, dynamic exec is CommonJS wrapper pattern. ai
phantom-deps phantom-dep:clipanion AI (phantom-deps): clipanion is bundled into dist/bin.js by esbuild; not a phantom dependency. ai

Versions (showing 4 of 4)

Version Deps Published
0.2.3 2 / 4
0.2.1 2 / 4
0.2.0 2 / 4
0.1.3 2 / 4

v0.2.3

2 findings
HIGH Publisher changed: jbuzaid-airtable → GitHub Actions (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

2 findings
HIGH New file with network + code execution: dist/bin.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.