@cyanheads/pubmed-mcp-server
MCP server for PubMed/NCBI E-utilities integration. Search articles, fetch metadata and open-access full text (PMC + Unpaywall), generate citations, explore MeSH terms, and discover related research.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:partial-json | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:fast-xml-parser | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:@supabase/supabase-js | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-node | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:pdf-lib | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:node-cron | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:papaparse | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:validator | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:@hono/otel | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| phantom-deps | phantom-dep:chrono-node | AI (phantom-deps): Bun-bundled project; deps imported in src, not dist. Stable FP. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 59 versions and 336 days of history; lack of provenance attestation is consistent across all versions and is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:sanitize-html | AI (dependencies): sanitize-html is a well-known, widely-used HTML sanitization library. Its use in a PubMed content server is appropriate and poses no security concern. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Bundled package; phantom-dep flag is a build artifact, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:defuddle | AI (phantom-deps): Bundled package; phantom-dep flag is a build artifact, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:unpdf | AI (phantom-deps): Package uses bun bundler; deps declared in package.json may be bundled or conditionally imported in source. Not indicative of malicious behavior. | ai | |
| phantom-deps | phantom-dep:sanitize-html | AI (phantom-deps): Bundled package; phantom-dep flag is a build artifact, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:linkedom | AI (phantom-deps): Bundled package; phantom-dep flag is a build artifact, not a security signal for this package. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 2.9.1 | 8 / 10 | |
| 2.9.0 | 8 / 10 | |
| 2.8.0 | 8 / 10 | |
| 2.7.11 | 8 / 10 | |
| 2.7.10 | 8 / 10 | |
| 2.7.9 | 8 / 10 | |
| 2.7.8 | 8 / 10 | |
| 2.7.7 | 8 / 10 | |
| 2.7.6 | 8 / 10 | |
| 2.7.5 | 8 / 10 | |
| 2.7.4 | 8 / 10 | |
| 2.7.3 | 8 / 10 | |
| 2.7.2 | 8 / 10 | |
| 2.7.1 | 7 / 10 | |
| 2.7.0 | 7 / 10 | |
| 2.6.12 | 7 / 10 | |
| 2.6.11 | 7 / 10 | |
| 2.6.10 | 7 / 10 | |
| 2.6.9 | 7 / 10 | |
| 2.6.8 | 7 / 10 | |
| 2.6.7 | 7 / 10 | |
| 2.6.6 | 7 / 10 | |
| 2.6.5 | 7 / 10 | |
| 2.6.4 | 7 / 9 | |
| 2.6.3 | 7 / 9 | |
| 2.6.2 | 7 / 9 | |
| 2.6.1 | 7 / 9 | |
| 2.6.0 | 7 / 9 | |
| 2.5.6 | 4 / 9 | |
| 2.5.5 | 4 / 9 | |
| 2.5.4 | 4 / 9 | |
| 2.5.3 | 4 / 9 | |
| 2.5.2 | 4 / 9 | |
| 2.5.0 | 4 / 9 | |
| 2.4.1 | 4 / 9 | |
| 2.4.0 | 4 / 9 | |
| 2.3.10 | 4 / 9 | |
| 2.3.9 | 4 / 9 | |
| 2.3.8 | 4 / 9 | |
| 2.3.4 | 4 / 9 | |
| 2.3.3 | 4 / 9 | |
| 2.3.2 | 4 / 8 | |
| 2.3.1 | 4 / 8 | |
| 2.3.0 | 4 / 8 | |
| 2.2.5 | 4 / 8 | |
| 2.2.4 | 4 / 8 | |
| 2.2.3 | 4 / 8 | |
| 2.2.2 | 4 / 8 | |
| 2.2.1 | 4 / 8 | |
| 2.2.0 | 4 / 8 | |
| 2.1.6 | 30 / 30 | |
| 2.1.5 | 30 / 30 | |
| 2.1.4 | 30 / 30 | |
| 2.1.3 | 30 / 30 | |
| 2.1.2 | 30 / 30 | |
| 2.1.1 | 30 / 30 | |
| 2.1.0 | 30 / 30 | |
| 2.0.1 | 30 / 30 |
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.