@platforma-open/milaboratories.runenv-python-3
Python 3 run environments for Platforma Backend
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established org package with strong publisher track record; provenance regression is minor and not indicative of malicious activity. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-pgen | AI (phantom-deps): Same-org scope dep used as a block-software entrypoint reference, not directly imported in JS — stable pattern for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Package consistently adds new same-org Python runtime variant deps across versions; pattern is stable and expected. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.10.11 | AI (phantom-deps): Meta-package references deps via JSON config paths, not JS imports; phantom-dep is a stable false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentionally tiny meta/aggregator package; no repo link is consistent with org-internal tooling pattern across 90 versions. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-humanness | AI (phantom-deps): Meta-package pattern; deps are referenced via block-software config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-clustering | AI (phantom-deps): Meta-package pattern; deps are referenced via block-software config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-torch-cuda | AI (phantom-deps): Meta-package pattern; deps are referenced via block-software config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-h5ad | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-atls | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-parapred | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-sccoda | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-rapids | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10-scientific-slim | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.runenv-python-3.12.10 | AI (phantom-deps): Same-org aggregator package; deps are declarative entrypoint references, not JS imports. | ai |
Versions (showing 97 of 97)
| Version | Deps | Published |
|---|---|---|
| 1.11.5 | 11 / 1 | |
| 1.11.4 | 11 / 1 | |
| 1.11.3 | 11 / 1 | |
| 1.11.2 | 11 / 1 | |
| 1.11.1 | 11 / 1 | |
| 1.11.0 | 11 / 1 | |
| 1.10.7 | 10 / 1 | |
| 1.10.6 | 10 / 1 | |
| 1.10.5 | 10 / 1 | |
| 1.10.4 | 10 / 1 | |
| 1.10.3 | 10 / 1 | |
| 1.10.2 | 10 / 1 | |
| 1.10.1 | 10 / 1 | |
| 1.10.0 | 10 / 1 | |
| 1.9.1 | 9 / 1 | |
| 1.9.0 | 8 / 1 | |
| 1.8.8 | 7 / 1 | |
| 1.8.7 | 7 / 1 | |
| 1.8.6 | 7 / 1 | |
| 1.8.5 | 7 / 1 | |
| 1.8.4 | 7 / 1 | |
| 1.8.3 | 7 / 1 | |
| 1.8.2 | 7 / 1 | |
| 1.8.1 | 7 / 1 | |
| 1.8.0 | 7 / 1 | |
| 1.7.12 | 6 / 1 | |
| 1.7.11 | 6 / 1 | |
| 1.7.10 | 6 / 1 | |
| 1.7.9 | 6 / 1 | |
| 1.7.8 | 6 / 1 | |
| 1.7.7 | 5 / 1 | |
| 1.7.6 | 5 / 1 | |
| 1.7.5 | 5 / 1 | |
| 1.7.4 | 5 / 1 | |
| 1.7.3 | 5 / 1 | |
| 1.7.2 | 5 / 1 | |
| 1.7.0 | 5 / 1 | |
| 1.6.3 | 5 / 1 | |
| 1.6.2 | 6 / 1 | |
| 1.6.1 | 6 / 1 | |
| 1.6.0 | 6 / 1 | |
| 1.5.12 | 5 / 1 | |
| 1.5.11 | 5 / 1 | |
| 1.5.10 | 5 / 1 | |
| 1.5.9 | 5 / 1 | |
| 1.5.8 | 5 / 1 | |
| 1.5.7 | 5 / 1 | |
| 1.5.6 | 5 / 1 | |
| 1.5.5 | 5 / 1 | |
| 1.5.4 | 5 / 1 | |
| 1.5.3 | 5 / 1 | |
| 1.5.2 | 5 / 1 | |
| 1.5.1 | 5 / 1 | |
| 1.5.0 | 5 / 1 | |
| 1.4.16 | 4 / 1 | |
| 1.4.15 | 4 / 1 | |
| 1.4.14 | 4 / 1 | |
| 1.4.13 | 4 / 1 | |
| 1.4.12 | 4 / 1 | |
| 1.4.11 | 4 / 1 | |
| 1.4.10 | 4 / 1 | |
| 1.4.9 | 4 / 1 | |
| 1.4.8 | 4 / 1 | |
| 1.4.7 | 4 / 1 | |
| 1.4.6 | 4 / 1 | |
| 1.4.5 | 3 / 1 | |
| 1.4.4 | 3 / 1 | |
| 1.4.3 | 3 / 1 | |
| 1.4.2 | 3 / 1 | |
| 1.4.1 | 3 / 1 | |
| 1.4.0 | 3 / 1 | |
| 1.3.1 | 3 / 1 | |
| 1.3.0 | 3 / 1 | |
| 1.2.5 | 3 / 1 | |
| 1.2.4 | 3 / 1 | |
| 1.2.3 | 3 / 1 | |
| 1.2.2 | 2 / 1 | |
| 1.2.1 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.17 | 0 / 3 | |
| 1.1.16 | 0 / 3 | |
| 1.1.15 | 0 / 3 | |
| 1.1.14 | 0 / 3 | |
| 1.1.13 | 0 / 3 | |
| 1.1.12 | 0 / 3 | |
| 1.1.11 | 0 / 3 | |
| 1.1.10 | 0 / 3 | |
| 1.1.9 | 0 / 3 | |
| 1.1.7 | 0 / 3 | |
| 1.1.6 | 0 / 3 | |
| 1.1.5 | 0 / 3 | |
| 1.1.4 | 0 / 3 | |
| 1.1.3 | 0 / 3 | |
| 1.1.2 | 0 / 3 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.0 | 0 / 3 |
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-05-07, but mike-ainsel 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.8.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-05-07, but mike-ainsel 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.8.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-05-07, but mike-ainsel 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.8.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-05-05, but mike-ainsel 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.8.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-05-04, but mike-ainsel 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.8.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-04-24, but mike-ainsel 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.7.12
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-04-23, but mike-ainsel 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.7.11
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-04-22, but mike-ainsel 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.7.10
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-04-10, but mike-ainsel 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.7.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-03-06, but mike-ainsel 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.7.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mike-ainsel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-09, but mike-ainsel 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.7.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dbolotin_mi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.