@lavamoat/preinstall-always-fail
Advanced tools
Comparing version 2.0.0 to 2.1.0
# Changelog | ||
## [2.1.0](https://github.com/LavaMoat/LavaMoat/compare/preinstall-always-fail-v2.0.0...preinstall-always-fail-v2.1.0) (2024-07-11) | ||
### Features | ||
* **allow-scripts:** support Node.js v22 ([0c665ec](https://github.com/LavaMoat/LavaMoat/commit/0c665ec65b635c29f347369809680372c9b58b79)) | ||
## [2.0.0](https://github.com/LavaMoat/LavaMoat/compare/preinstall-always-fail-v1.0.3...preinstall-always-fail-v2.0.0) (2023-10-18) | ||
@@ -4,0 +11,0 @@ |
{ | ||
"name": "@lavamoat/preinstall-always-fail", | ||
"version": "2.0.0", | ||
"version": "2.1.0", | ||
"description": "", | ||
"main": "index.js", | ||
"scripts": { | ||
"test": "exit 0", | ||
"preinstall": "echo \"Don't run npm lifecycle scripts by default! Create a .yarnrc or .npmrc and set enableScripts: false. Then, whitelist them with @lavamoat/allow-scripts\" && exit 1" | ||
}, | ||
"repository": { | ||
"type": "git", | ||
"url": "https://github.com/LavaMoat/LavaMoat.git", | ||
"url": "git+https://github.com/LavaMoat/LavaMoat.git", | ||
"directory": "packages/preinstall-always-fail" | ||
}, | ||
"publishConfig": { | ||
"access": "public" | ||
}, | ||
"keywords": [], | ||
"author": "", | ||
"license": "MIT", | ||
"engines": { | ||
"node": "^16.20.0 || ^18.0.0 || ^20.0.0" | ||
"node": "^16.20.0 || ^18.0.0 || ^20.0.0 || ^22.0.0" | ||
}, | ||
"keywords": [], | ||
"scripts": { | ||
"preinstall": "echo \"Don't run npm lifecycle scripts by default! Create a .yarnrc or .npmrc and set enableScripts: false. Then, whitelist them with @lavamoat/allow-scripts\" && exit 1", | ||
"test": "exit 0" | ||
}, | ||
"publishConfig": { | ||
"access": "public" | ||
} | ||
} |
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
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
3526
2