@cyanheads/brapi-mcp-server
BrAPI v2.1 MCP server — studies, germplasm, observations, genotypes, images, and pedigrees.
Supply chain provenance
Status for the latest visible version.
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
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): zod is a well-known, widely-used validation library; no risk generalizes from this addition. | ai | |
| dependencies | unvetted-dep:@duckdb/node-api | AI (dependencies): @duckdb/node-api is the official DuckDB Node.js binding; legitimate dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has a clean track record; lack of Sigstore attestation is a process gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is commonly used as a transport/formatter referenced in config rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@duckdb/node-api | AI (phantom-deps): DuckDB may be loaded conditionally or via config; phantom-dep heuristic is unreliable for this pattern. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.6.4 | 4 / 7 | |
| 0.6.1 | 3 / 7 | |
| 0.6.0 | 3 / 7 | |
| 0.5.5 | 3 / 7 | |
| 0.5.4 | 3 / 7 | |
| 0.5.3 | 3 / 7 | |
| 0.5.2 | 3 / 7 | |
| 0.5.1 | 3 / 7 | |
| 0.5.0 | 3 / 7 | |
| 0.4.14 | 2 / 8 | |
| 0.4.13 | 2 / 8 | |
| 0.4.12 | 2 / 8 | |
| 0.4.11 | 2 / 8 | |
| 0.4.10 | 2 / 8 | |
| 0.4.9 | 2 / 7 | |
| 0.4.8 | 2 / 7 | |
| 0.4.7 | 2 / 7 | |
| 0.4.6 | 2 / 7 | |
| 0.4.5 | 2 / 7 | |
| 0.4.4 | 2 / 7 | |
| 0.4.3 | 2 / 7 | |
| 0.4.2 | 2 / 7 | |
| 0.4.1 | 2 / 7 | |
| 0.3.9 | 2 / 7 | |
| 0.3.8 | 2 / 7 | |
| 0.3.7 | 2 / 7 | |
| 0.3.6 | 2 / 7 | |
| 0.3.5 | 2 / 8 |
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.