accept

v3.1.3

HTTP Accept-* headers parsing For more information about how to use this package see README

Latest version published 4 years ago
License: BSD-3-Clause

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

53 / 100

Explore Similar Packages

Security

No known security issues
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
3.1.3 | 11/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.2 | 11/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.1.4 | 05/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0 | 07/2015
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 10/2014
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
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

Recognized

Weekly Downloads (97,431)

Download trend
Dependents
32
GitHub Stars
48
Forks
31
Contributors
20

Direct Usage Popularity

TOP 30%

The npm package accept receives a total of 97,431 downloads a week. As such, we scored accept popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package accept, we found that it has been starred 48 times, and that 32 other projects in 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.

Community

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

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
0
Last Release
4 years ago
Last Commit
7 months ago

Further analysis of the maintenance status of accept 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 accept 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
9 years
Dependencies
2 Direct
Versions
17
Install Size
17.2 kB
Dist-tags
1
# of Files
9
Maintainers
1
TS Typings
Yes

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