generic-filehandle 1.0.9

[![NPM version](https://img.shields.io/npm/v/generic-filehandle.svg?style=flat-square)](https://npmjs.org/package/generic-filehandle) [![Build Status](https://travis-ci.com/GMOD/generic-filehandle.svg?branch=master)](https://travis-ci.com/GMOD/generic-fil

generic-filehandle@1.0.9 was published on 2019-05-01. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=6.

All generic-filehandle versions · Permanent reference to 1.0.9 · Latest release

Package specifications

Version1.0.9
License declarationMIT
Published2019-05-01T21:01:12.394Z
Node.js requirement>=6
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size60.19 KiB
Published file count16
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars5
Repository forks6

Install generic-filehandle 1.0.9

npm install generic-filehandle@1.0.9
pnpm add generic-filehandle@1.0.9
yarn add generic-filehandle@1.0.9

Runtime dependencies

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 1/30 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Maintained2/10 — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
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
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness