@cyanheads/git-mcp-server
A secure and scalable Git MCP server enabling AI agents to perform comprehensive Git version control operations via STDIO and Streamable HTTP.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): pino/cross-spawn/pino-pretty are established logging/process libs, used as declared. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Encoded strings are pdf-lib bundled font/compression data, not obfuscated payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Bundling pdf-lib and other deps into dist explains size growth. | ai | |
| phantom-deps | phantom-dep:@types/validator | AI (phantom-deps): Type definitions loaded by convention; paired with validator dependency. | ai | |
| phantom-deps | phantom-dep:@types/sanitize-html | AI (phantom-deps): Type definitions loaded by convention; paired with sanitize-html dependency. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type definitions loaded by convention; standard for Node.js packages. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build-time dependency; referenced in scripts and tsconfig. Stable pattern for TypeScript packages. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Build-time dependency; used in scripts. Stable pattern for TypeScript packages. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Declared dependency; used via build externals and runtime logging. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Declared dependency; used via build externals for log formatting. | ai | |
| phantom-deps | phantom-dep:cross-spawn | AI (phantom-deps): Declared dependency; used for subprocess spawning in Git operations. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 3 / 45 | |
| 2.14.2 | 3 / 45 | |
| 2.14.0 | 3 / 45 | |
| 2.13.0 | 3 / 45 | |
| 2.12.0 | 3 / 45 | |
| 2.11.1 | 3 / 45 | |
| 2.11.0 | 3 / 45 | |
| 2.10.6 | 3 / 45 | |
| 2.10.2 | 3 / 45 | |
| 2.8.4 | 3 / 62 | |
| 2.8.1 | 3 / 62 | |
| 2.8.0 | 3 / 62 | |
| 2.7.0 | 3 / 62 | |
| 2.6.3 | 3 / 62 | |
| 2.6.0 | 2 / 61 | |
| 2.3.5 | 17 / 20 | |
| 2.3.4 | 17 / 19 | |
| 2.3.3 | 17 / 18 | |
| 2.3.2 | 17 / 16 | |
| 2.3.1 | 17 / 16 | |
| 2.2.4 | 19 / 10 | |
| 2.2.3 | 19 / 10 | |
| 2.2.2 | 19 / 2 | |
| 2.2.1 | 19 / 2 | |
| 2.2.0 | 19 / 2 | |
| 2.1.8 | 19 / 2 | |
| 2.1.7 | 19 / 2 | |
| 2.1.6 | 19 / 2 | |
| 2.1.5 | 19 / 2 |
v2.10.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cyanheads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.