The npm package babel-plugin-transform-dead-code-elimination receives a total of 117 downloads a week. As such, we scored babel-plugin-transform-dead-code-elimination popularity level to be Limited.
Based on project statistics from the GitHub repository for the npm package babel-plugin-transform-dead-code-elimination, we found that it has been starred 8 times, and that 25 other projects on the ecosystem are dependent on it.
Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.
You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.
We found a way for you to contribute to the project! Looks like babel-plugin-transform-dead-code-elimination is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test babel-plugin-transform-dead-code-elimination
Further analysis of the maintenance status of babel-plugin-transform-dead-code-elimination based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.
An important project maintenance signal to consider for babel-plugin-transform-dead-code-elimination is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.
In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.
This project has seen only 10 or less contributors.
We found a way for you to contribute to the project! Looks like babel-plugin-transform-dead-code-elimination is missing a Code of Conduct.
We detected a total of 7 direct & transitive dependencies for babel-plugin-transform-dead-code-elimination. See the full dependency tree of babel-plugin-transform-dead-code-elimination
babel-plugin-transform-dead-code-elimination has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.