@oxide/api
Advanced tools
+1
-1
| { | ||
| "name": "@oxide/api", | ||
| "version": "0.5.0", | ||
| "version": "0.5.1", | ||
| "description": "TypeScript client for the Oxide API", | ||
@@ -5,0 +5,0 @@ "engines": { |
+3
-6
@@ -19,3 +19,3 @@ # `@oxide/api` | ||
| | --- | --- | --- | | ||
| | [18](https://docs.oxide.computer/release-notes/system/18) | 0.5.0 | `rel18` | | ||
| | [18](https://docs.oxide.computer/release-notes/system/18) | 0.5.1 | `rel18` | | ||
@@ -38,8 +38,5 @@ ## Usage | ||
| Then print the token: | ||
| You can find the generated token in `~/.config/oxide/credentials.toml` | ||
| (`%USERPROFILE%\.config\oxide\credentials.toml` on Windows). | ||
| ``` | ||
| oxide auth status --show-token | ||
| ``` | ||
| In the following example, the token is passed to the script through the | ||
@@ -46,0 +43,0 @@ `OXIDE_TOKEN` environment variable on the assumption that you don't want to |
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
1208774
0.01%151
-1.95%