Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
@azure/core-xml
Advanced tools
This library is primarily intended to be used in code generated by AutoRest and autorest.typescript
for APIs that require parsing XML payloads.
See our support policy for more details.
This package is primarily used in generated code and not meant to be consumed directly by end users.
XML parsing is mostly delegated to the browser and xml2js
.
Examples can be found in the samples
folder.
See @azure/core-client
for actual usage.
If you run into issues while using this library, please feel free to file an issue.
If you'd like to contribute to this library, please read the contributing guide to learn more about how to build and test the code.
FAQs
Core library for interacting with XML payloads
The npm package @azure/core-xml receives a total of 1,044,092 weekly downloads. As such, @azure/core-xml popularity was classified as popular.
We found that @azure/core-xml demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.