@vechain/sdk-errors — Greenflagged

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

freemanzmrojovanjat7vechaibdarren_vechainfabiorigamdavide.carpinicnealvechainroisindowlingfbarufgiuliamorg92agilulfodomkaspermikeredmondberk-vechainvictor-vechaindoublemmedara-vechain

Keywords

VeChainerror

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established VeChain Foundation SDK package; lack of provenance attestation is a process gap, not a security indicator for this package.	ai	2026/04/27

Versions (showing 8 of 8)

Version	Deps	Published
2.0.7	0 / 0	2025-11-20
2.0.6	0 / 0	2025-11-12
2.0.5	0 / 0	2025-09-05
2.0.4	0 / 0	2025-08-15
2.0.3	0 / 0	2025-08-07
2.0.2	0 / 0	2025-07-25
2.0.1	0 / 0	2025-07-21
2.0.0	0 / 0	2025-06-30

v2.0.7

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.

v2.0.6

2 findings

HIGH Publisher changed: cnealvechain → giuliamorg92 (on 2025-11-12) provenance

This version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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