@solidjs/signals 0.13.13

SolidJS' standalone reactivity implementation

@solidjs/signals@0.13.13 was published on 2026-04-14. Its manifest declares 0 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 @solidjs/signals versions · Permanent reference to 0.13.13 · Latest release

Package specifications

Version0.13.13
License declarationMIT
Published2026-04-14T22:24:49.746Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size348.62 KiB
Published file count33
Package typemodule
ES module entrydist/prod.js
Default entrydist/node.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars36174
Repository forks1136

Install @solidjs/signals 0.13.13

npm install @solidjs/signals@0.13.13
pnpm add @solidjs/signals@0.13.13
yarn add @solidjs/signals@0.13.13

Runtime dependencies

  • None declared

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.

Maintained10/10 — 29 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Code-Review2/10 — Found 6/21 approved changesets -- score normalized to 2
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness