@cyanheads/secedgar-mcp-server
Query SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & 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 — 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:node-cron | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:domhandler | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance not yet enabled; low-risk package with clean publisher history. | ai | |
| dependencies | unvetted-dep:@duckdb/node-api | AI (dependencies): @duckdb/node-api is the official DuckDB Node.js API; legitimate native binding, not a supply-chain risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): zod is a widely-used, well-established validation library; not a supply-chain risk here. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is a logging transport typically referenced in config/options, not directly imported; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@duckdb/node-api | AI (phantom-deps): DuckDB may be loaded via dynamic import or abstraction layer; phantom-dep heuristic is unreliable for this usage pattern. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 11 / 8 | |
| 0.7.3 | 11 / 8 | |
| 0.7.2 | 10 / 8 | |
| 0.7.1 | 8 / 8 | |
| 0.7.0 | 8 / 8 | |
| 0.6.2 | 5 / 8 | |
| 0.6.1 | 5 / 8 | |
| 0.6.0 | 5 / 8 | |
| 0.5.2 | 5 / 8 | |
| 0.5.1 | 4 / 8 | |
| 0.5.0 | 4 / 8 | |
| 0.4.5 | 3 / 8 | |
| 0.4.4 | 3 / 8 | |
| 0.4.3 | 3 / 8 | |
| 0.4.2 | 3 / 8 | |
| 0.4.1 | 3 / 8 | |
| 0.4.0 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.2.0 | 3 / 8 | |
| 0.1.11 | 3 / 8 | |
| 0.1.10 | 3 / 8 | |
| 0.1.9 | 3 / 8 |
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.