
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@umerx/reconnecting-websocket
Advanced tools
Resilient web socket that automatically reconnects if the connection is closed.
Commit changes to git.
In the project root directory, run npm version <update_type>
to update the version number in package.json
. Replace <update_type>
with one of the semantic versioning release types (patch, minor, or major).
Push to GitHub. Jenkins is configured to build and publish the package to npm on every push to the main
branch.
Check your package page (https://www.npmjs.com/package/@umerx/reconnecting-websocket
) to check that the package version has been updated.
FAQs
Reconnecting WebSocket
We found that @umerx/reconnecting-websocket 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
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.