ronomon-queue
Advanced tools
ronomon-queue - npm Package Compare versions
Comparing version 3.0.0 to 4.0.0
| { | ||
| "name": "ronomon-queue", | ||
| "version": "3.0.0", | ||
| "description": "Process thousands of asynchronous or synchronous jobs, concurrently or sequentially, safely and efficiently, without creating thousands of closures.", | ||
| "version": "4.0.0", | ||
| "description": "", | ||
| "main": "index.js", | ||
| "scripts": { | ||
| "test": "echo \"Error: no test specified\" && exit 1" | ||
| }, | ||
| "repository": { | ||
| "type": "git", | ||
| "url": "git+https://github.com/jorangreef/ronomon-queue.git" | ||
| "url": "git+https://github.com/npm/deprecate-holder.git" | ||
| }, | ||
| "keywords": [ | ||
| "abort", | ||
| "array", | ||
| "async", | ||
| "asynchronous", | ||
| "callback", | ||
| "cb", | ||
| "closure", | ||
| "concurrency", | ||
| "concurrent", | ||
| "control", | ||
| "control flow", | ||
| "each", | ||
| "error", | ||
| "flow", | ||
| "flow control", | ||
| "foreach", | ||
| "iterate", | ||
| "loop", | ||
| "map", | ||
| "parallel", | ||
| "queue", | ||
| "sequential", | ||
| "serial", | ||
| "series", | ||
| "stop", | ||
| "stream", | ||
| "sync", | ||
| "synchronous", | ||
| "terminate", | ||
| "throttle", | ||
| "utility" | ||
| ], | ||
| "author": "Joran Dirk Greef", | ||
| "license": "MIT", | ||
| "author": "", | ||
| "license": "ISC", | ||
| "bugs": { | ||
| "url": "https://github.com/jorangreef/ronomon-queue/issues" | ||
| "url": "https://github.com/npm/deprecate-holder/issues" | ||
| }, | ||
| "homepage": "https://github.com/jorangreef/ronomon-queue#readme", | ||
| "scripts": { | ||
| "test": "node test.js" | ||
| } | ||
| "homepage": "https://github.com/npm/deprecate-holder#readme" | ||
| } |
@@ -1,3 +0,5 @@ | ||
| # ronomon-queue | ||
| # Deprecated Package | ||
| Moved to https://github.com/ronomon/queue | ||
| This package is no longer supported and has been deprecated. To avoid malicious use, npm is hanging on to the package name. | ||
| Please contact support@npmjs.com if you have questions about this package. |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
Found 1 instance in 1 package
No tests
QualityPackage does not have any tests. This is a strong signal of a poorly maintained or low quality package.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
Found 1 instance in 1 package
No website
QualityPackage does not have a website.
Found 1 instance in 1 package
Improved metrics
- Number of lines in readme file
- increased by50%
6
Worsened metrics
- Total package byte prevSize
- decreased by-95.68%
676
- Number of package files
- decreased by-71.43%
2
- Lines of code
- decreased by-100%
0
- Number of medium supply chain risk alerts
- increased byInfinity%
3