@autoxing/robot-js-sdk-dev
AutoXing SDK
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 51 of 93)
| Version | Deps | Published |
|---|---|---|
| 1.1.254 | 0 / 13 | |
| 1.1.253 | 0 / 13 | |
| 1.1.252 | 0 / 13 | |
| 1.1.251 | 0 / 13 | |
| 1.1.250 | 0 / 13 | |
| 1.1.249 | 0 / 13 | |
| 1.1.248 | 0 / 13 | |
| 1.1.247 | 0 / 13 | |
| 1.1.246 | 0 / 13 | |
| 1.1.245 | 0 / 13 | |
| 1.1.244 | 0 / 13 | |
| 1.1.243 | 0 / 13 | |
| 1.1.242 | 0 / 13 | |
| 1.1.241 | 0 / 13 | |
| 1.1.240 | 0 / 13 | |
| 1.1.239 | 0 / 13 | |
| 1.1.238 | 0 / 13 | |
| 1.1.237 | 0 / 13 | |
| 1.1.236 | 0 / 13 | |
| 1.1.235 | 0 / 13 | |
| 1.1.234 | 0 / 13 | |
| 1.1.233 | 0 / 13 | |
| 1.1.232 | 0 / 13 | |
| 1.1.231 | 0 / 13 | |
| 1.1.230 | 0 / 13 | |
| 1.1.229 | 0 / 13 | |
| 1.1.228 | 0 / 13 | |
| 1.1.227 | 0 / 13 | |
| 1.1.226 | 0 / 13 | |
| 1.1.225 | 0 / 13 | |
| 1.1.224 | 0 / 13 | |
| 1.1.223 | 0 / 13 | |
| 1.1.222 | 0 / 13 | |
| 1.1.221 | 0 / 13 | |
| 1.1.219 | 0 / 13 | |
| 1.1.218 | 0 / 13 | |
| 1.1.217 | 0 / 13 | |
| 1.1.216 | 0 / 13 | |
| 1.1.215 | 0 / 13 | |
| 1.1.214 | 0 / 13 | |
| 1.1.213 | 0 / 13 | |
| 1.1.212 | 0 / 13 | |
| 1.1.211 | 0 / 13 | |
| 1.1.210 | 0 / 13 | |
| 1.1.209 | 0 / 13 | |
| 1.1.208 | 0 / 13 | |
| 1.1.207 | 0 / 13 | |
| 1.1.206 | 0 / 13 | |
| 1.1.205 | 0 / 13 | |
| 1.1.204 | 0 / 13 | |
| 1.1.203 | 0 / 13 |
v1.1.254
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.208
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (z-alger) than the most recent previously approved version (liuting009) on 2025-04-21, but z-alger is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.207
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liuting009) than the most recent previously approved version (z-alger) on 2025-04-07, but liuting009 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.