expressling

v0.1.6

Expressling For more information about how to use this package see README

Latest version published 13 years ago
License: MIT

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

50 / 100

Explore Similar Packages

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
0.1.6 | 04/2012
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.9 | 12/2011
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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

Small

Weekly Downloads (2)

Download trend
GitHub Stars
2.28K
Forks
153
Contributors
20

Direct Usage Popularity


The npm package expressling receives a total of 2 downloads a week. As such, we scored expressling popularity level to be Small.

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

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

Community

Active
Readme.md
No
Contributing.md
No
Code of Conduct
Yes
Contributors
20
Funding
Yes

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

How about a good first contribution to this project? It seems that expressling is missing a README file.


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
6
Open PR
39
Last Release
13 years ago
Last Commit
3 years ago

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

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>= 0.6.3

Age
13 years
Dependencies
21 Direct
Versions
17
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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