browser-sync-client 2.27.12

Client-side scripts for BrowserSync

browser-sync-client@2.27.12 was published on 2023-02-23. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.0.0.

All browser-sync-client versions · Permanent reference to 2.27.12 · Latest release

Package specifications

Version2.27.12
License declarationISC
Published2023-02-23T12:39:45.616Z
Node.js requirement>=8.0.0
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size148.47 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository stars39
Repository forks42

Install browser-sync-client 2.27.12

npm install browser-sync-client@2.27.12
pnpm add browser-sync-client@2.27.12
yarn add browser-sync-client@2.27.12

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.

Code-Review1/10 — Found 3/23 approved changesets -- score normalized to 1
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness