
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
@pnpm/check-package
Advanced tools
Checks the integrity of a package
When pnpm saves a package to the store, it creates an integrity.json
file.
integrity.json
contains a hash for each file of the package.
@pnpm/check-package
can check whether the resources of the package were modified, using integrity.json
.
Install it via npm.
npm install @pnpm/npm-resolver
'use strict'
const checkPackage = require('@pnpm/check-package').default
checkPackage('test/fixtures/good/pkg')
.then(ok => {
console.log(Boolean(ok))
//> true
})
.catch(err => console.error(err))
checkPackage(packagePath) => Promise<matchedIntegrity | false>
If the package has been touched, false
is returned. If the package has its "canonical" form, the content
of integrity.json
is returned.
FAQs
Checks the integrity of a package
The npm package @pnpm/check-package receives a total of 11 weekly downloads. As such, @pnpm/check-package popularity was classified as not popular.
We found that @pnpm/check-package demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.