rustpython-vm
RustPython virtual machine.
Activity
- Latest release
- 3w ago
- Total releases
- 8
- Cadence
- ~7 months
- Last 12 months
- 2
Reach
- Downloads
- 145.5k
Details
- License
- MIT
- First release
- Jul 07, 2019
| Version | Released | |
|---|---|---|
0.6.0
minor
|
0.6.0
minor
Dependencies (55)
+ 47 more
Changelog
Compare changes
|
|
0.5.0
unknown
1 CVE
RUSTSEC-2026-0394
Sep 23, 2026
Build environment compiled into the library and readable at runtime The build script of A binary built in CI with secrets in the environment carries those secrets
in clear text. Registry tokens, cloud credentials and API keys are the usual
ones. Anyone with the binary can read them with Version 0.6.0 removes the dump and the include. Users of earlier versions should upgrade, rebuild, and ship new binaries. Every secret that was in the environment of a past build whose output left the build machine should be treated as exposed. Jacob Finkelman first reported the issue in #8802. Bitbison's automated supply chain scanning then detected credential data from the build environment flowing into artifacts that third-party software ships in the wild. The leak was confirmed in the published release binaries of at least four dependants but others have been impacted. Fixed in
0.6.0
References Updated Oct 26, 2026 · Source: OSV.dev |
0.5.0
unknown
Dependencies (69)
+ 61 more
Changelog
Compare changes
|
|
0.4.0
unknown
1 CVE
RUSTSEC-2026-0394
Sep 23, 2026
Build environment compiled into the library and readable at runtime The build script of A binary built in CI with secrets in the environment carries those secrets
in clear text. Registry tokens, cloud credentials and API keys are the usual
ones. Anyone with the binary can read them with Version 0.6.0 removes the dump and the include. Users of earlier versions should upgrade, rebuild, and ship new binaries. Every secret that was in the environment of a past build whose output left the build machine should be treated as exposed. Jacob Finkelman first reported the issue in #8802. Bitbison's automated supply chain scanning then detected credential data from the build environment flowing into artifacts that third-party software ships in the wild. The leak was confirmed in the published release binaries of at least four dependants but others have been impacted. Fixed in
0.6.0
References Updated Oct 26, 2026 · Source: OSV.dev | ||
0.3.1
unknown
1 CVE
RUSTSEC-2026-0394
Sep 23, 2026
Build environment compiled into the library and readable at runtime The build script of A binary built in CI with secrets in the environment carries those secrets
in clear text. Registry tokens, cloud credentials and API keys are the usual
ones. Anyone with the binary can read them with Version 0.6.0 removes the dump and the include. Users of earlier versions should upgrade, rebuild, and ship new binaries. Every secret that was in the environment of a past build whose output left the build machine should be treated as exposed. Jacob Finkelman first reported the issue in #8802. Bitbison's automated supply chain scanning then detected credential data from the build environment flowing into artifacts that third-party software ships in the wild. The leak was confirmed in the published release binaries of at least four dependants but others have been impacted. Fixed in
0.6.0
References Updated Oct 26, 2026 · Source: OSV.dev | ||
0.3.0
unknown
1 CVE
RUSTSEC-2026-0394
Sep 23, 2026
Build environment compiled into the library and readable at runtime The build script of A binary built in CI with secrets in the environment carries those secrets
in clear text. Registry tokens, cloud credentials and API keys are the usual
ones. Anyone with the binary can read them with Version 0.6.0 removes the dump and the include. Users of earlier versions should upgrade, rebuild, and ship new binaries. Every secret that was in the environment of a past build whose output left the build machine should be treated as exposed. Jacob Finkelman first reported the issue in #8802. Bitbison's automated supply chain scanning then detected credential data from the build environment flowing into artifacts that third-party software ships in the wild. The leak was confirmed in the published release binaries of at least four dependants but others have been impacted. Fixed in
0.6.0
References Updated Oct 26, 2026 · Source: OSV.dev | ||
0.1.2
unknown
yanked
|
0.1.2
unknown
yanked
Dependencies (84)
+ 76 more
Changelog
Compare changes
|
|
0.1.1
unknown
yanked
|
0.1.1
unknown
yanked
Dependencies (59)
+ 51 more
Changelog
Compare changes
|
|
0.1.0
unknown
yanked
|