bytebuffer

v5.0.1

The swiss army knife for binary data in JavaScript.

Apache-2.0
Latest version published 6 years ago
    npm install bytebuffer
  

Package Health Score

68 / 100

Security

No known security issues
Powered by Snyk
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
5.0.1 | 02/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.1.0 | 09/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.5.5 | 06/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.3.2 | 08/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.2.0 | 12/2013
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test bytebuffer
Get started free

Popularity

Popular

Weekly Downloads (515,191)

Download trend
Dependents
679
GitHub Stars
681
Forks
152
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package bytebuffer receives a total of 515,191 downloads a week. As such, we scored bytebuffer popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package bytebuffer, we found that it has been starred 681 times, and that 679 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
No
Contributors
20
Funding
No

With more than 10 contributors for the bytebuffer 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 bytebuffer is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 68/100 package health 68/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
35
Open PR
5
Last Release
6 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of bytebuffer 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 bytebuffer 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
>=0.8

Age
9 years
Dependencies
1 Direct
Versions
69
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

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