@e-llm-studio/data-engine
data operations library for e-llm-studio
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has clean 62/0 track record; no code changes accompany the switch. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same maintainer transition, consistent with legitimate org handoff. | ai | |
| phantom-deps | phantom-dep:http | AI (phantom-deps): Declared but not imported; refers to Node.js built-in, not the stub package. | ai | |
| dependencies | unvetted-dep:http | AI (dependencies): npm security placeholder stub; not actually imported per phantom-dep finding. | ai | |
| phantom-deps | phantom-dep:stream | AI (phantom-deps): Declared but not imported; refers to Node.js built-in stream module. | ai | |
| phantom-deps | phantom-dep:Buffer | AI (phantom-deps): Declared but not imported; Buffer is a Node.js global, not a real dep. | ai | |
| dependencies | unvetted-dep:Buffer | AI (dependencies): npm polyfill stub at 0.0.0; not actually imported per phantom-dep finding. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 6 / 3 | |
| 1.3.2 | 2 / 2 | |
| 1.3.1 | 2 / 2 | |
| 1.3.0 | 1 / 2 | |
| 1.2.0 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.0 | 1 / 2 |
v1.3.2
2 findingsThis version was published by a different npm account than previous versions on 2025-02-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-02-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.