@samverschueren/stream-to-observable

Convert Node Streams into ECMAScript-Observables

@samverschueren/stream-to-observable@0.3.1 was published on 2020-08-09. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.

All @samverschueren/stream-to-observable versions · Permanent reference to 0.3.1 · View npm registry JSON

Package specifications

Version0.3.1
License declarationMIT
Published2020-08-09T11:06:18.791Z
Node.js requirement>=6
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.93 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars3
Repository forks7

Install @samverschueren/stream-to-observable 0.3.1

npm install @samverschueren/stream-to-observable@0.3.1
pnpm add @samverschueren/stream-to-observable@0.3.1
yarn add @samverschueren/stream-to-observable@0.3.1

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 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
SAST0/10 — no SAST tool detected
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness