vscode-css-languageservice 4.0.0-next.3

Language service for CSS, LESS and SCSS

vscode-css-languageservice@4.0.0-next.3 was published on 2019-03-05. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All vscode-css-languageservice versions · Permanent reference to 4.0.0-next.3 · Latest release

Package specifications

Version4.0.0-next.3
License declarationMIT
Published2019-03-05T11:09:16.651Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2237.25 KiB
Published file count81
Package typeNot declared
ES module entry./lib/esm/cssLanguageService.js
Default entry./lib/umd/cssLanguageService.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars388
Repository forks223

Install vscode-css-languageservice 4.0.0-next.3

npm install vscode-css-languageservice@4.0.0-next.3
pnpm add vscode-css-languageservice@4.0.0-next.3
yarn add vscode-css-languageservice@4.0.0-next.3

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.

Security-Policy10/10 — security policy file detected
Maintained6/10 — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
SAST7/10 — SAST tool is not run on all commits -- score normalized to 7

Evidence and freshness