Alert
Unable to verify the project's public source code repository.

assign

v0.1.7

Map/Reduce promise like returned API -- Really not way to properly describe this module..

MIT
Latest version published 7 years ago
    npm install assign
  

Package Health Score

42 / 100

Popularity

Recognized

Weekly Downloads (12,736)

Download trend
Dependents
1
GitHub Stars
?
Forks
?
Contributors
-

Direct Usage Popularity

Uncommon

The npm package assign receives a total of 12,736 downloads a week. As such, we scored assign popularity level to be Recognized.

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

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

01/2014
11/2014

Direct Vulnerabilities

0.0.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.1.7
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.1.7

License Risk

0.0.2
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.1.7
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like assign is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test assign
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Unavailable commit data
Open Issues
?
Open PR
?
Last Release
7 years ago
Last Commit
unknown

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

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
0
Funding
No

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 42/100 package health 42/100

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
1 Direct
Versions
12
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
5
TS Typings
No

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