autoprefixer 1.0.20131222

Parse CSS and add vendor prefixes to CSS rules using values from the Can I Use website

autoprefixer@1.0.20131222 was published on 2013-12-22. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All autoprefixer versions · Permanent reference to 1.0.20131222 · Latest release

Package specifications

Version1.0.20131222
License declarationMIT
Published2013-12-22T02:46:38.639Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
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 entryNot declared
Default entrylib/autoprefixer
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies7
Repository stars22203
Repository forks1290

Install autoprefixer 1.0.20131222

npm install autoprefixer@1.0.20131222
pnpm add autoprefixer@1.0.20131222
yarn add autoprefixer@1.0.20131222

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/30 approved changesets -- score normalized to 1
Maintained10/10 — 25 commit(s) and 2 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
Pinned-Dependencies10/10 — all dependencies are pinned
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
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness