webpack-subresource-integrity 1.1.0-rc.2

Webpack plugin for enabling Subresource Integrity

webpack-subresource-integrity@1.1.0-rc.2 was published on 2018-02-28. Its manifest declares 1 runtime dependency and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.

All webpack-subresource-integrity versions · Permanent reference to 1.1.0-rc.2 · Latest release

Package specifications

Version1.1.0-rc.2
License declarationMIT
Published2018-02-28T15:12:06.534Z
Node.js requirement>=4
Type declarationsNot declared
Runtime dependency count1
Peer requirement count1
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size30.83 KiB
Published file count57
Package typeNot declared
ES module entryNot declared
Default entryindex
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies48
Repository stars374
Repository forks46

Install webpack-subresource-integrity 1.1.0-rc.2

npm install webpack-subresource-integrity@1.1.0-rc.2
pnpm add webpack-subresource-integrity@1.1.0-rc.2
yarn add webpack-subresource-integrity@1.1.0-rc.2

Runtime dependencies

Peer requirements

Optional dependencies

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.

Code-Review10/10 — all changesets reviewed
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
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
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