optimizer

v1.8.4

Module to support the optimized delivery of web application resources For more information about how to use this package see README

Latest version published 9 years ago
License: Apache License v2.0

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

46 / 100

Security

Security review needed
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
1.8.4 | 09/2015
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.7.1 | 02/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.6.2 | 01/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.5.9 | 01/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.14 | 11/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache License v2.0
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (32)

Download trend
GitHub Stars
582
Forks
75
Contributors
30

Direct Usage Popularity

TOP 30%

The npm package optimizer receives a total of 32 downloads a week. As such, we scored optimizer popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package optimizer, we found that it has been starred 582 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
30
Funding
No

With more than 10 contributors for the optimizer repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like optimizer is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 46/100 package health 46/100

Maintenance

Inactive

Commit Frequency

Open Issues
88
Open PR
4
Last Release
9 years ago
Last Commit
9 months ago

Further analysis of the maintenance status of optimizer 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 optimizer 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.

Package

Node.js Compatibility
not defined

Age
10 years
Dependencies
27 Direct
Versions
83
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
5
TS Typings
Yes

optimizer 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.