Comparing version 0.0.0 to 0.0.1-security
{ | ||
"name": "fs", | ||
"version": "0.0.0", | ||
"version": "0.0.1-security", | ||
"description": "", | ||
@@ -9,4 +9,13 @@ "main": "index.js", | ||
}, | ||
"repository": { | ||
"type": "git", | ||
"url": "git+https://github.com/npm/security-holder.git" | ||
}, | ||
"keywords": [], | ||
"author": "", | ||
"license": "MIT" | ||
"license": "ISC", | ||
"bugs": { | ||
"url": "https://github.com/npm/security-holder/issues" | ||
}, | ||
"homepage": "https://github.com/npm/security-holder#readme" | ||
} |
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
Known malware
Supply chain riskThis package is malware. We have asked the package registry to remove it.
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
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 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 bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
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 website
QualityPackage does not have a website.
Found 1 instance in 1 package
794
2
2
2
0
10
0
1
2