faye 0.6.4
Simple pub/sub messaging for the web
faye@0.6.4 was published on 2011-08-17. 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 >=0.1.96.
All faye versions · Permanent reference to 0.6.4 · Latest release
Package specifications
| Version | 0.6.4 |
|---|---|
| License declaration | Not declared |
| Published | 2011-08-17T23:41:39.941Z |
| Node.js requirement | >=0.1.96 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | ./faye-node |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 4383 |
| Repository forks | 367 |
Install faye 0.6.4
npm install faye@0.6.4 pnpm add faye@0.6.4 yarn add faye@0.6.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.
- @redis/bloom@6.3.0 — indirect
- @redis/client@6.3.0 — indirect
- @redis/json@6.3.0 — indirect
- @redis/search@6.3.0 — indirect
- @redis/time-series@6.3.0 — indirect
- redis@6.3.0 — direct
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.
| Code-Review | 1/10 — Found 3/29 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| License | 9/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/faye/0.6.4 — retrieved 2026-10-29T21:47:48.063Z
- https://api.deps.dev/v3/projects/github.com%2Ffaye%2Ffaye — retrieved 2026-10-29T20:10:28.956Z
- https://api.deps.dev/v3/systems/npm/packages/faye/versions/0.6.4 — retrieved 2026-10-29T21:47:48.622Z
- https://api.deps.dev/v3/systems/npm/packages/faye/versions/0.6.4:dependencies — retrieved 2026-10-29T21:47:48.630Z