postcss-import-resolver 1.2.3

Customize postcss-import resolve with enhanced-resolve

postcss-import-resolver@1.2.3 was published on 2019-05-14. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All postcss-import-resolver versions · Permanent reference to 1.2.3 · Latest release

Package specifications

Version	1.2.3
License declaration	MIT
Published	2019-05-14T17:53:06.754Z
Node.js requirement	Not declared
Type declarations	Bundled declarations
Runtime dependency count	1
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	64.06 KiB
Published file count	7
Package type	Not declared
ES module entry	Not declared
Default entry	index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	15
Repository stars	9
Repository forks	1

Install postcss-import-resolver 1.2.3

npm install postcss-import-resolver@1.2.3
pnpm add postcss-import-resolver@1.2.3
yarn add postcss-import-resolver@1.2.3

Runtime dependencies

enhanced-resolve ^3.4.1

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.

core-util-is@1.0.3 — indirect
enhanced-resolve@3.4.1 — direct
errno@0.1.8 — indirect
graceful-fs@4.2.11 — indirect
inherits@2.0.4 — indirect
isarray@1.0.0 — indirect
memory-fs@0.4.1 — indirect
object-assign@4.1.1 — indirect
process-nextick-args@2.0.1 — indirect
prr@1.0.1 — indirect
readable-stream@2.3.8 — indirect
safe-buffer@5.1.2 — indirect
string_decoder@1.1.1 — indirect
tapable@0.2.9 — indirect
util-deprecate@1.0.2 — indirect

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.

Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	10/10 — no binaries found in the repo
Code-Review	0/10 — Found 1/18 approved changesets -- score normalized to 0
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Pinned-Dependencies	0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing	0/10 — project is not fuzzed
Security-Policy	0/10 — security policy file not detected
License	10/10 — license file detected
Branch-Protection	0/10 — branch protection not enabled on development/release branches
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/postcss-import-resolver/1.2.3 — retrieved 2026-10-29T08:06:31.988Z
https://api.deps.dev/v3/systems/npm/packages/postcss-import-resolver/versions/1.2.3 — retrieved 2026-10-29T08:06:32.435Z
https://api.deps.dev/v3/systems/npm/packages/postcss-import-resolver/versions/1.2.3:dependencies — retrieved 2026-10-29T08:06:32.501Z
https://api.deps.dev/v3/projects/github.com%2Fclarkdo%2Fpostcss-import-resolver — retrieved 2026-10-29T08:06:33.079Z