← Home

@premai/prem-rs

npm
6
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

lorenzodalmazzofederico-prem

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:prem_rs_main.js AI (source-diff): File is wasm-bindgen generated JS glue code; network+exec pattern is standard WASM binding, not malware. ai
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI is a standard, legitimate CI/CD migration pattern. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is standard wasm-bindgen generated glue code; stable false positive for this WASM binding package. ai
bogus-package bogus-package AI (bogus-package): WASM binding auto-published via CI; no repo link, keywords, or deps is normal for this package type. ai

Versions (showing 6 of 6)

Version Deps Published
0.3.0 0 / 0
0.2.7 0 / 0
0.2.6 0 / 0
0.2.4 0 / 0
0.2.3 0 / 0
0.2.2 0 / 0

v0.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

3 findings
HIGH Publisher changed: federico-prem → GitHub Actions (on 2026-04-10) provenance

This version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: prem_rs_main.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.