babel-plugin-danger-remove-unused-import

[![Build status](https://img.shields.io/travis/imcuttle/babel-plugin-danger-remove-unused-import/master.svg?style=flat-square)](https://travis-ci.org/imcuttle/babel-plugin-danger-remove-unused-import) [![Test coverage](https://img.shields.io/codecov/c/git

babel-plugin-danger-remove-unused-import@2.0.0 was published on 2019-09-09. Its manifest declares 0 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 babel-plugin-danger-remove-unused-import versions · Permanent reference to 2.0.0

Package specifications

Version2.0.0
License declarationMIT
Published2019-09-09T09:09:17.891Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size10.19 KiB
Published file count7
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars19
Repository forks6

Install babel-plugin-danger-remove-unused-import 2.0.0

npm install babel-plugin-danger-remove-unused-import@2.0.0
pnpm add babel-plugin-danger-remove-unused-import@2.0.0
yarn add babel-plugin-danger-remove-unused-import@2.0.0

Runtime dependencies

  • None declared

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-Review0/10 — Found 1/23 approved changesets -- score normalized to 0
    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
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    Fuzzing0/10 — project is not fuzzed
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    License10/10 — license file detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness