styled-components 2.3.1

Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅

styled-components@2.3.1 was published on 2017-12-19. Its manifest declares 8 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All styled-components versions · Permanent reference to 2.3.1 · Latest release

Package specifications

Version2.3.1
License declarationMIT
Published2017-12-19T09:17:31.425Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count8
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entrydist/styled-components.es.js
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies31
Repository stars41062
Repository forks2613

Install styled-components 2.3.1

npm install styled-components@2.3.1
pnpm add styled-components@2.3.1
yarn add styled-components@2.3.1

Runtime dependencies

Peer requirements

  • react >= 0.14.0 < 17.0.0-0

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-Review0/10 — Found 0/12 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts9/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness