← Home

@lwc/errors

LWC Error Utilities

26
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

lwc-admincaridyjye-sfravi.jayaramappajodaroveabdulsattarrax-it1lpomerleau

Keywords

lwc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Salesforce LWC monorepo migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI/CD provenance. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal consistent with org-level CI publishing transition for this Salesforce package. ai

Versions (showing 26 of 26)

Version Deps Published
9.3.6 0 / 0
9.3.5 0 / 0
9.3.4 0 / 0
9.2.2 0 / 0
9.2.1 0 / 0
9.2.0 0 / 0
9.1.5 0 / 0
9.1.4 0 / 0
9.1.3 0 / 0
9.1.2 0 / 0
9.1.1 0 / 0
9.1.0 0 / 0
9.0.3 0 / 0
9.0.2 0 / 0
9.0.1 0 / 0
9.0.0 0 / 0
8.28.2 0 / 0
8.28.1 0 / 0
8.28.0 0 / 0
8.27.0 0 / 0
8.26.2 0 / 0
8.26.1 0 / 0
8.26.0 0 / 0
8.25.1 0 / 0
8.25.0 0 / 0
8.24.0 0 / 0

v9.3.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v9.3.5

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: lwc-admin → GitHub Actions (on 2026-07-17, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (lwc-admin) on 2026-07-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.