
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
A simple wrapper around Node's regular require function that makes it easy
to require file relative to the current script in a platform agnostic manner.
const introduce = require('introduce')();
const foo = introduce('lib', 'foo.js');
const bar = introduce('lib', 'bar'); // could be .js or .json
const foobar = introduce(['lib', 'subdir', 'foobar']);
// paths work as well
const relativeFoo = introduce('./lib/foo');
const winFoo = introduce('lib\\foo');
// Includes within includes pose a problem. Node sets the parent of the
// innermost include to the outermost module. Thus, if '/foo.js' includes
// '/lib/bar.js' which includes '/lib/sublib/baz.js', then the second include
// would try to load '/baz.js'. To fix that silliness:
const introduce = require('introduce')(__dirname);
const bar = introduce('lib/bar');
FAQs
A platform agnostic require wrapper
The npm package introduce receives a total of 19 weekly downloads. As such, introduce popularity was classified as not popular.
We found that introduce demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.