@cnakazawa/watch

Utilities for watching file trees.

@cnakazawa/watch@1.0.4 was published on 2020-02-11. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.1.95.

All @cnakazawa/watch versions · Permanent reference to 1.0.4

Package specifications

Version1.0.4
License declarationApache-2.0
Published2020-02-11T23:22:37.776Z
Node.js requirement>=0.1.95
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified size2.44 KiB
Minified + gzip1.02 KiB
Unpacked distribution size24.47 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entry./main
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars1283
Repository forks150

Install @cnakazawa/watch 1.0.4

npm install @cnakazawa/watch@1.0.4
pnpm add @cnakazawa/watch@1.0.4
yarn add @cnakazawa/watch@1.0.4

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.

Binary-Artifacts10/10 — no binaries found in the repo
Code-Review2/10 — Found 7/29 approved changesets -- score normalized to 2
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
License10/10 — license file 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