flow-annotation-check 1.10.0

Check your files for the presence of the `@flow` and `@flow weak` annotations

flow-annotation-check@1.10.0 was published on 2018-12-06. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^8 || >=10.

All flow-annotation-check versions · Permanent reference to 1.10.0 · View npm registry JSON · Latest release

Package specifications

Version1.10.0
License declarationMIT
Published2018-12-06T06:10:22.562Z
Node.js requirement^8 || >=10
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size41.62 KiB
Published file count16
Package typeNot declared
ES module entryNot declared
Default entry./lib/flow-annotation-check.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies26
Repository stars3
Repository forks2

Install flow-annotation-check 1.10.0

npm install flow-annotation-check@1.10.0
pnpm add flow-annotation-check@1.10.0
yarn add flow-annotation-check@1.10.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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.

Maintained0/10 — project is archived
Code-Review0/10 — Found 1/17 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License0/10 — license file not detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness