
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.
This is the readme file for the npm package. It covers only information specific to the npm package. Wed's real README is visible in the git repository. It also has extensive documentation.
This npm package does not allow you to do require('wed') in your
application. Wed is designed to run in browsers, not in Node. So why
this package?
It provides a convenient way to distribute the built wed tree.
The tool wed-metadata does run in Node. Some
projects using wed might need to use it. This package provides a way
to install the tool.
This package contains the following:
bin/wed-metadata: the tool mentioned above.
standalone: a standalone build of wed. This build contains
everything needed to load wed, including third-party libraries.
packed: a Webpack build of the previous tree.
FAQs
Wed is a schema-aware editor for XML documents.
The npm package wed receives a total of 46 weekly downloads. As such, wed popularity was classified as not popular.
We found that wed 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.