@mlflow/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:bundle/daemon.cjs | AI (source-diff): esbuild bundle banner for documented CLI daemon binary, not true obfuscation. | ai | |
| source-diff | net-exec-file:bundle/daemon.cjs | AI (source-diff): OTLP trace exporter daemon legitimately does network I/O; bundled, not a dropper. | ai | |
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions publisher is a CI/CD provenance improvement. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @mlflow/core is the official MLflow scoped package, not a typo of cors; name similarity is coincidental. | ai | |
| phantom-deps | phantom-dep:ini | AI (phantom-deps): ini is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
v0.3.0
4 findingsThis version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.