@xuda.io/runtime-bundle
The Xuda Runtime Bundle refers to a collection of scripts and libraries packaged together to provide the necessary runtime environment for executing plugins or components in the Xuda platform.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval in bundled parser/template modules; consistent pattern across 1450 versions of this runtime bundle. | ai | |
| phantom-deps | phantom-dep:json5 | AI (phantom-deps): Declared dep consumed by bundled code, not direct imports. | ai | |
| phantom-deps | phantom-dep:klona | AI (phantom-deps): Declared dep consumed by bundled code, not direct imports. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared dep consumed by bundled code, not direct imports. | ai | |
| phantom-deps | phantom-dep:pouchdb | AI (phantom-deps): Declared dep consumed by bundled code, not direct imports. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.1456 | 4 / 0 | |
| 1.0.1455 | 4 / 0 | |
| 1.0.1454 | 4 / 0 | |
| 1.0.1453 | 4 / 0 | |
| 1.0.1452 | 4 / 0 | |
| 1.0.1451 | 4 / 0 | |
| 1.0.1450 | 4 / 0 | |
| 1.0.1449 | 4 / 0 | |
| 1.0.1448 | 4 / 0 | |
| 1.0.1447 | 4 / 0 | |
| 1.0.1446 | 4 / 0 | |
| 1.0.1445 | 4 / 0 | |
| 1.0.1444 | 4 / 0 | |
| 1.0.1443 | 4 / 0 | |
| 1.0.1442 | 4 / 0 | |
| 1.0.1441 | 4 / 0 | |
| 1.0.1440 | 4 / 0 | |
| 1.0.1439 | 4 / 0 | |
| 1.0.1438 | 4 / 0 | |
| 1.0.1437 | 4 / 0 |
v1.0.1456
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1455
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1454
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1453
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1452
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1451
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1450
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1449
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1448
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1447
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1446
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1445
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1444
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1443
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1442
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1441
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1440
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1439
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1438
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1437
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.