← Home

@pi-unipi/updater

npm Repository Homepage
15
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

neuron-mr-white

Keywords

pi-packagepi-extensionpi-coding-agentunipiupdaterchangelogreadme

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Spreading process.env into a child process exec call is standard practice for an updater/installer utility; not exfiltration. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm packages); not a risk signal for this package. ai

Versions (showing 15 of 15)

Version Deps Published
2.0.12 1 / 2
2.0.11 1 / 2
2.0.10 1 / 2
2.0.9 1 / 2
2.0.8 1 / 2
2.0.7 1 / 2
2.0.6 1 / 2
2.0.5 1 / 2
2.0.4 1 / 2
2.0.3 1 / 2
2.0.2 1 / 2
2.0.1 1 / 2
2.0.0 1 / 2
0.1.2 1 / 2
0.1.1 1 / 2

v2.0.12

1 finding
INFO No provenance attestation provenance

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

v2.0.11

1 finding
INFO No provenance attestation provenance

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

v2.0.10

1 finding
INFO No provenance attestation provenance

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

v2.0.9

1 finding
INFO No provenance attestation provenance

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

v2.0.8

1 finding
INFO No provenance attestation provenance

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

v2.0.7

1 finding
INFO No provenance attestation provenance

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

v2.0.6

1 finding
INFO No provenance attestation provenance

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

v2.0.5

1 finding
INFO No provenance attestation provenance

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

v2.0.4

1 finding
INFO No provenance attestation provenance

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

v2.0.3

1 finding
INFO No provenance attestation provenance

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

v2.0.2

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

2 findings
HIGH env-spread: src/installer.ts:34 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Neuron-Mr-White/unipi/blob/40601bdb1f4595fbed0daf7a66c7f51866758aaa/src/installer.ts#L34 32 | { 33 | timeout: INSTALL_TIMEOUT_MS, > 34 | env: { ...process.env }, 35 | }, 36 | );

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.1.2

2 findings
HIGH env-spread: src/installer.ts:34 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Neuron-Mr-White/unipi/blob/78ef1f2e36c237b7b9ed56e83eb4862d8bf86304/src/installer.ts#L34 32 | { 33 | timeout: INSTALL_TIMEOUT_MS, > 34 | env: { ...process.env }, 35 | }, 36 | );

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.1.1

2 findings
HIGH env-spread: src/installer.ts:35 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Neuron-Mr-White/unipi/blob/037803d998209266e700ce0802f9221f46123aa5/src/installer.ts#L35 33 | { 34 | timeout: INSTALL_TIMEOUT_MS, > 35 | env: { ...process.env }, 36 | }, 37 | );

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.