convert-svg-core 0.6.3

Supports converting SVG into another format using headless Chromium

convert-svg-core@0.6.3 was published on 2022-06-06. Its manifest declares 11 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^12.20.0 || >=14.

Deprecated: version 0.6.4 and below are no longer supported

All convert-svg-core versions · Permanent reference to 0.6.3 · View npm registry JSON · Latest release

Package specifications

Version0.6.3
License declarationMIT
Published2022-06-06T11:04:02.129Z
Node.js requirement^12.20.0 || >=14
Type declarationsNot declared
Runtime dependency count11
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size49.57 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies98
Repository stars199
Repository forks48

Install convert-svg-core 0.6.3

npm install convert-svg-core@0.6.3
pnpm add convert-svg-core@0.6.3
yarn add convert-svg-core@0.6.3

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.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review0/10 — Found 0/15 approved changesets -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
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
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Pinned-Dependencies1/10 — dependency not pinned by hash detected -- score normalized to 1
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness