virtual-dom

v2.1.1

A batched diff-based DOM rendering strategy

MIT
Latest version published 7 years ago
    npm install virtual-dom
  
We couldn't find any similar packages Browse all packages

Package Health Score

56 / 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
2.1.1 | 08/2015
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.1 | 03/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.0 | 01/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.24 | 12/2014
  • 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 virtual-dom
Get started free

Popularity

Popular

Weekly Downloads (21,383)

Download trend
Dependents
568
GitHub Stars
11.38K
Forks
812
Contributors
30

Direct Usage Popularity

TOP 30%

The npm package virtual-dom receives a total of 21,383 downloads a week. As such, we scored virtual-dom popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package virtual-dom, we found that it has been starred 11,378 times, and that 568 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
30
Funding
No

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


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
111
Open PR
46
Last Release
7 years ago
Last Commit
6 years ago

Further analysis of the maintenance status of virtual-dom 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 virtual-dom 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
8 years
Dependencies
8 Direct
Versions
32
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

virtual-dom 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.