
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.
@oxide/api
Advanced tools
npm install @oxide/api
The easiest way to get a device token is to use the CLI.
oxide auth login --host https://my-oxide-rack.com
Then print the token:
oxide auth status --show-token
In the following example it's passed to the script through the OXIDE_TOKEN
environment variable on the assumption that you don't want to hard-code a token
into a script, but this can of course be done however you want. OXIDE_TOKEN is
not a special variable for the TypeScript SDK (it is for the CLI).
import Oxide from "@oxide/api"
const oxide = new Oxide({
host: "https://my-oxide-rack.com",
token: process.env.OXIDE_TOKEN,
})
const result = await oxide.methods.projectList({})
if (result.type === "success") {
console.log(result.data.items.map((p) => p.name))
}
ApiResult<T>FAQs
TypeScript client for the Oxide API
The npm package @oxide/api receives a total of 11 weekly downloads. As such, @oxide/api popularity was classified as not popular.
We found that @oxide/api demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 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
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.