@cyanheads/git-mcp-server Apache-2.0 22 versions

@cyanheads/git-mcp-server

npm Repository Homepage

A secure and scalable Git MCP server enabling AI agents to perform comprehensive Git version control operations via STDIO and Streamable HTTP.

22

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

cyanheads

Keywords

ai-agentai-integrationautomationbranchcherry-pickclonecommitdevopsdifffetchgitgit-toolsllmllm-toolslogmcpmcp-servermergemodel-context-protocolpullpushrebaseremoteresetstashstatustagtypescriptversion-controlworktree

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/sanitize-html	AI (phantom-deps): Type definitions loaded by convention; paired with sanitize-html dependency.	ai	2026/05/13
phantom-deps	phantom-dep:ts-node	AI (phantom-deps): Build-time dependency; used in scripts. Stable pattern for TypeScript packages.	ai	2026/05/13
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): Type definitions loaded by convention; standard for Node.js packages.	ai	2026/05/13
phantom-deps	phantom-dep:@types/validator	AI (phantom-deps): Type definitions loaded by convention; paired with validator dependency.	ai	2026/05/13
phantom-deps	phantom-dep:typescript	AI (phantom-deps): Build-time dependency; referenced in scripts and tsconfig. Stable pattern for TypeScript packages.	ai	2026/05/13
phantom-deps	phantom-dep:cross-spawn	AI (phantom-deps): Declared dependency; used for subprocess spawning in Git operations.	ai	2026/05/01
phantom-deps	phantom-dep:pino-pretty	AI (phantom-deps): Declared dependency; used via build externals for log formatting.	ai	2026/05/01
phantom-deps	phantom-dep:pino	AI (phantom-deps): Declared dependency; used via build externals and runtime logging.	ai	2026/05/01

Versions (showing 22 of 22)

Version	Deps	Published
2.15.0	3 / 45	2026-04-29
2.14.2	3 / 45	2026-04-24
2.14.0	3 / 45	2026-04-24
2.13.0	3 / 45	2026-04-23
2.12.0	3 / 45	2026-04-23
2.11.1	3 / 45	2026-04-21
2.11.0	3 / 45	2026-04-19
2.10.6	3 / 45	2026-04-19
2.3.5	17 / 20	2025-09-29
2.3.4	17 / 19	2025-09-26
2.3.3	17 / 18	2025-09-15
2.3.2	17 / 16	2025-07-31
2.3.1	17 / 16	2025-07-31
2.2.4	19 / 10	2025-07-29
2.2.3	19 / 10	2025-07-29
2.2.2	19 / 2	2025-07-21
2.2.1	19 / 2	2025-07-18
2.2.0	19 / 2	2025-07-16
2.1.8	19 / 2	2025-06-30
2.1.7	19 / 2	2025-06-29
2.1.6	19 / 2	2025-06-29
2.1.5	19 / 2	2025-06-29

v2.14.2

1 finding

LOW No provenance attestation provenance

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

v2.14.0

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.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.

v2.11.0

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.

v2.10.6

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.

v2.3.5

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.

v2.3.4

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.

v2.3.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.

v2.3.2

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.

v2.3.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.

v2.2.4

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.

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

v2.2.2

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.

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

v2.2.0

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.

v2.1.8

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.

v2.1.7

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.

v2.1.6

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.

v2.1.5

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.