libp2p-floodsub 0.3.0

libp2p-floodsub, also known as pubsub-flood or just dumbsub, this implementation of pubsub focused on delivering an API for Publish/Subscribe, but with no CastTree Forming (it just floods the network).

libp2p-floodsub@0.3.0 was published on 2016-09-14. Its manifest declares 7 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All libp2p-floodsub versions · Permanent reference to 0.3.0 · Latest release

Package specifications

Version	0.3.0
License declaration	MIT
Published	2016-09-14T16:51:21.556Z
Node.js requirement	Not declared
Type declarations	Not declared
Runtime dependency count	7
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	Not supplied
Published file count	Not supplied
Package type	Not declared
ES module entry	Not declared
Default entry	lib/core/index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	18
Repository stars	47
Repository forks	17

Install libp2p-floodsub 0.3.0

npm install libp2p-floodsub@0.3.0
pnpm add libp2p-floodsub@0.3.0
yarn add libp2p-floodsub@0.3.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.

buffer-alloc-unsafe@1.1.0 — indirect
core-util-is@1.0.3 — indirect
debug@2.6.9 — direct
git-sha1@0.1.2 — direct
inherits@2.0.4 — indirect
isarray@1.0.0 — indirect
length-prefixed-stream@1.6.0 — direct
lodash.intersection@4.4.0 — direct
lodash.uniq@4.5.0 — direct
lodash.values@4.3.0 — direct
ms@2.0.0 — indirect
process-nextick-args@2.0.1 — indirect
readable-stream@2.3.8 — indirect
safe-buffer@5.1.2 — indirect
string_decoder@1.1.1 — indirect
time-cache@0.2.3 — direct
util-deprecate@1.0.2 — indirect
varint@5.0.2 — indirect

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.

Maintained	0/10 — project is archived
Code-Review	3/10 — Found 8/26 approved changesets -- score normalized to 3
Binary-Artifacts	10/10 — no binaries found in the repo
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies	3/10 — dependency not pinned by hash detected -- score normalized to 3
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing	0/10 — project is not fuzzed
License	9/10 — license file detected
Branch-Protection	0/10 — branch protection not enabled on development/release branches
Security-Policy	0/10 — security policy file not detected
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/libp2p-floodsub/0.3.0 — retrieved 2026-10-30T19:33:53.679Z
https://api.deps.dev/v3/systems/npm/packages/libp2p-floodsub/versions/0.3.0:dependencies — retrieved 2026-10-30T19:33:54.171Z
https://api.deps.dev/v3/systems/npm/packages/libp2p-floodsub/versions/0.3.0 — retrieved 2026-10-30T19:33:54.368Z
https://api.deps.dev/v3/projects/github.com%2Flibp2p%2Fjs-libp2p-floodsub — retrieved 2026-10-30T19:33:54.676Z