Is hyparquet safe?
What hyparquet does
hyparquet is a JavaScript library that reads Apache Parquet files in the browser or Node.js, with no dependencies. It is published on npm by Hyperparam from the hyparam/hyparquet repository under the MIT license. It reads remote files over HTTP with range requests, so it fetches only the parts it needs, and reads local files in Node.js through asyncBufferFromFile. You can pass fetch headers for authentication and pick rows and columns to limit what is downloaded, and read a file's metadata and schema on their own. Writing Parquet files is left to the separate hyparquet-writer package. Before installing, keep any authorization headers you pass in requestInit out of browser code that users can read.
- Node.js network egress
- npm prepare hook
What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.
hyparquet is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: install time execution and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
hyparquet 1.33.0
Get notified when this component changes
Change alerts aren't live yet. Leave your email and we'll let you know when they launch. We use it only for this and delete it on request.
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of hyparquet's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (2)
package.json has a 'prepare' script (runs on git/local installs and before publishing).
"prepare": "npm run build:types",
Why it matters: Usually a build step, but confirm it doesn't fetch or run remote code.
Fix: Usually a legitimate build step; confirm it only builds and does not fetch or execute remote code.
The component makes outbound network requests.
const res = await fetch(url, { ...requestInit, method: 'HEAD' })const res = await fetch(url, { ...init, headers })Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
How attackers abuse these capabilities
Interactive labs on the attack class behind the rules above. They show the technique, not anything found in hyparquet.
Maintain hyparquet?
The free Claude Code plugin scans each npm, PyPI or MCP package with this report's open-source engine before the install command runs. It runs on your machine and needs no account.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →