Comparing version 0.1.0 to 0.1.1
Missing package tarball
QualityThis package is missing its tarball. It could be removed from the npm registry or there may have been an error when publishing.
Found 1 instance in 1 package
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
Wildcard dependency
QualityPackage has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version.
Found 2 instances in 1 package
Native code
Supply chain riskContains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.
Found 35 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
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 v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
No website
QualityPackage does not have a website.
Found 1 instance in 1 package
Unmaintained
MaintenancePackage has not been updated in more than 5 years and may be unmaintained. Problems with the package may go unaddressed.
Found 1 instance in 1 package
0
0
0
0
0
0
0
0
0
0
0
1
0
- Removeddebug@*
- Removedreadable-stream@~0.0.3
- Removedstream-parser@*
- Removeddebug@2.6.94.4.0(transitive)
- Removedms@2.0.02.1.3(transitive)
- Removedreadable-stream@0.0.4(transitive)
- Removedstream-parser@0.3.1(transitive)