workerd - npm Package Compare versions
Comparing version 0.0.1 to 1.20220926.0
| { | ||
| "name": "workerd", | ||
| "description": "", | ||
| "author": "", | ||
| "version": "0.0.1", | ||
| "description": "👷 workerd, Cloudflare's JavaScript/Wasm Runtime", | ||
| "repository": "https://github.com/cloudflare/workerd", | ||
| "scripts": {}, | ||
| "main": "lib/main.js", | ||
| "engines": { | ||
| "node": ">=16" | ||
| }, | ||
| "bin": { | ||
| "workerd": "bin/workerd" | ||
| }, | ||
| "optionalDependencies": { | ||
| "@cloudflare/workerd-darwin-arm64": "1.20220926.0", | ||
| "@cloudflare/workerd-darwin-64": "1.20220926.0", | ||
| "@cloudflare/workerd-linux-arm64": "1.20220926.0", | ||
| "@cloudflare/workerd-linux-64": "1.20220926.0" | ||
| }, | ||
| "license": "Apache-2.0", | ||
| "main": "worker.js" | ||
| "version": "1.20220926.0" | ||
| } |
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
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
Network access
Supply chain riskThis module accesses the network.
Found 2 instances 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
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
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
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
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
No README
QualityPackage does not have a README. This may indicate a failed publish or a low quality package.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by14315.67%
19317
- Number of package files
- increased by400%
5
- Lines of code
- increased byInfinity%
354
- Number of low quality alerts
- decreased by-50%
1
- Number of medium quality alerts
- decreased by-100%
0
- Number of lines in readme file
- increased byInfinity%
7
Worsened metrics
- Dependency count
- increased byInfinity%
4
- Number of low supply chain risk alerts
- increased by700%
8
- Number of medium supply chain risk alerts
- increased by500%
6