xstream

v11.14.0

An extremely intuitive, small, and fast functional reactive stream library for JavaScript

MIT
Latest version published 2 years ago
    npm install xstream
  

Package Health Score

67 / 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
11.14.0 | 10/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.13.0 | 09/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.9.0 | 07/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.3.0 | 12/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.2.0 | 12/2016
  • 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.

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

Popularity

Popular

Weekly Downloads (19,101)

Download trend
Dependents
454
GitHub Stars
2.29K
Forks
138
Contributors
40

Direct Usage Popularity

TOP 30%

The npm package xstream receives a total of 19,101 downloads a week. As such, we scored xstream popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package xstream, we found that it has been starred 2,288 times, and that 454 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
Yes
Code of Conduct
No
Contributors
40
Funding
Yes

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


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Maintenance

Inactive

Commit Frequency

Open Issues
44
Open PR
3
Last Release
2 years ago
Last Commit
3 months ago

Further analysis of the maintenance status of xstream 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 xstream 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
6 years
Dependencies
2 Direct
Versions
103
Install Size
715 kB
Dist-tags
2
# of Files
45
Maintainers
2
TS Typings
Yes

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