re-reselect

v4.0.0

Enhance Reselect selectors with deeper memoization and cache management

MIT
Latest version published 2 years ago
    npm install re-reselect
  

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
4.0.0 | 05/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.4.0 | 07/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.3.0 | 12/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 08/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.6.3 | 08/2017
  • 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 re-reselect
Get started free

Popularity

Popular

Weekly Downloads (100,718)

Download trend
Dependents
88
GitHub Stars
1.01K
Forks
46
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package re-reselect receives a total of 100,718 downloads a week. As such, we scored re-reselect popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package re-reselect, we found that it has been starred 1,008 times, and that 88 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

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

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


Embed Package Health Score Badge

package health: 68/100 package health 68/100

Maintenance

Inactive

Commit Frequency

Open Issues
4
Open PR
3
Last Release
2 years ago
Last Commit
1 month ago

Further analysis of the maintenance status of re-reselect 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 re-reselect 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct
Versions
23
Install Size
203 kB
Dist-tags
1
# of Files
23
Maintainers
1
TS Typings
Yes

re-reselect 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.