@things-factory/mlops
MLOps module - ML lifecycle orchestration platform for Things-Factory
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@operato/app | AI (phantom-deps): Config-referenced peer dep in things-factory plugin architecture; stable pattern. | ai | |
| phantom-deps | phantom-dep:@operato/i18n | AI (phantom-deps): Config-referenced peer dep in things-factory plugin architecture; stable pattern. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Config-referenced peer dep in things-factory plugin architecture; stable pattern. | ai | |
| phantom-deps | phantom-dep:@operato/graphql | AI (phantom-deps): Config-referenced peer dep in things-factory plugin architecture; stable pattern. | ai | |
| phantom-deps | phantom-dep:@operato/data-grist | AI (phantom-deps): Config-referenced peer dep in things-factory plugin architecture; stable pattern. | ai | |
| phantom-deps | phantom-dep:@things-factory/integration-mlflow | AI (phantom-deps): Same-org scope dep; plugin architecture wires these via config. | ai | |
| phantom-deps | phantom-dep:@things-factory/integration-label-studio | AI (phantom-deps): Same-org scope dep; plugin architecture wires these via config. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 9.2.27 | 10 / 0 | |
| 9.2.26 | 10 / 0 | |
| 9.2.25 | 10 / 0 | |
| 9.2.19 | 10 / 0 | |
| 9.2.18 | 10 / 0 |
v9.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.