flow-parser 0.111.0

JavaScript parser written in OCaml. Produces ESTree AST

flow-parser@0.111.0 was published on 2019-10-30. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.4.0.

All flow-parser versions · Permanent reference to 0.111.0 · Latest release

Package specifications

Version0.111.0
License declarationMIT
Published2019-10-30T22:40:14.709Z
Node.js requirement>=0.4.0
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2521.10 KiB
Published file count3
Package typeNot declared
ES module entryNot declared
Default entryflow_parser.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars22306
Repository forks1892

Install flow-parser 0.111.0

npm install flow-parser@0.111.0
pnpm add flow-parser@0.111.0
yarn add flow-parser@0.111.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Security-Policy9/10 — security policy file detected
Branch-Protection1/10 — branch protection is not maximal on development and all release branches
SAST0/10 — no SAST tool detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness