@ampproject/rollup-plugin-closure-compiler 0.9.0

Rollup + Google Closure Compiler

@ampproject/rollup-plugin-closure-compiler@0.9.0 was published on 2019-04-15. Its manifest declares 6 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.

All @ampproject/rollup-plugin-closure-compiler versions · Permanent reference to 0.9.0 · View npm registry JSON · Latest release

Package specifications

Version0.9.0
License declarationApache-2.0
Published2019-04-15T04:23:19.809Z
Node.js requirement>=8
Type declarationsNot declared
Runtime dependency count6
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size115.51 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies42
Repository stars293
Repository forks28

Install @ampproject/rollup-plugin-closure-compiler 0.9.0

npm install @ampproject/rollup-plugin-closure-compiler@0.9.0
pnpm add @ampproject/rollup-plugin-closure-compiler@0.9.0
yarn add @ampproject/rollup-plugin-closure-compiler@0.9.0

Runtime dependencies

Peer requirements

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.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review3/10 — Found 11/30 approved changesets -- score normalized to 3
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy0/10 — security policy file not detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness