Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@pnpm/meta-updater
Advanced tools
Keeps meta files up-to-date in a monorepo
<pnpm|yarn|npm> add @pnpm/meta-updater
Create a JavaScript file at .meta-updater/main.mjs
that contains the updater functions.
The following .meta-updater/main.mjs
defines updaters for package.json
and tsconfig.json
files:
export default (workspaceDir) => {
return {
'package.json': (manifest, dir) => {
return {
...manifest,
author: 'Foo Bar',
}
},
'tsconfig.json': (tsConfig, dir) => {
return {
...tsConfig,
compilerOptions: {
outDir: 'lib',
rootDir: 'src',
},
}
},
}
}
The following .meta-updater/main.mjs
defines format #ignore
and updaters for .gitignore
and .eslintrc
using explicit format specifier.
import * as fs from 'fs/promises'
import { createFormat, createUpdateOptions } from '@pnpm/meta-updater'
/* default .eslintrc */
export const eslintrc = {}
/* default tsconfig.json */
export const tsconfig = { compilerOptions: { target: 'esnext' } }
/**
* User-defined format '#ignore'
*/
const ignoreFormat = createFormat({
async read({ resolvedPath }) {
return (await fs.readFile(resolvedPath, 'utf8')).split('\n')
},
update(actual, updater, options) {
return updater(actual, options)
},
equal(expected, actual) {
return R.equals(expected, actual)
},
async write(expected, { resolvedPath }) {
const unique = (array) => Array.from(new Set() < T[number] > array).sort()
await fs.writeFile(resolvedPath, unique(expected).join('\n'), 'utf8')
},
})
export default async (_workspaceDir) => {
return createUpdateOptions({
files: {
// builtin
'tsconfig.json': (actual, _options) => actual ?? tsconfig,
// buildin .json format with explicit format specifier
'.eslintrc [.json]': (actual) => actual ?? eslintrc,
// user-defined `#ignore` format
'.prettierignore [#ignore]': (actual) => actual ?? ['node_modules'],
},
formats: {
'#ignore': ignoreFormat,
},
})
}
See more examples at src/examples/
To perform the update on the affected config files, run pnpm meta-updater
.
To check that all meta files are up-to-date, run pnpm meta-updater --test
. It is recommended to always check the meta files before running the tests, so add it to your test command:
{
"test": "meta-updater --test && jest"
}
(config | null, dir, manifest) => Promise<config | null>
The updater function recieves the config object or null (if the config file does not exist). The updater function returns the config object that should be saved. If the updater function returns null, the config should be removed.
FAQs
Keeps meta files up-to-date in a monorepo
We found that @pnpm/meta-updater demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.