estado

v0.7.1

Simple JavaScript Finite State Machines. For more information about how to use this package see README

Latest version published 9 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

58 / 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
0.7.1 | 11/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.6.3 | 11/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.5.0 | 11/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.4 | 10/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.3.5 | 10/2015
  • 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 (23)

Download trend
GitHub Stars
26.5K
Forks
1.22K
Contributors
330

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package estado, we found that it has been starred 26,500 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
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
330
Funding
Yes

A good and healthy external contribution signal for estado project, which invites more than one hundred open source maintainers to collaborate on the repository.


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive

Commit Frequency

Open Issues
79
Open PR
49
Last Release
9 years ago
Last Commit
3 months ago

Further analysis of the maintenance status of estado 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 estado 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
1 Direct
Versions
22
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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