@lwc/engine-server
Renders LWC components in a server environment.
Supply chain provenance
Status for the latest visible version.
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): Transition from lwc-admin to GitHub Actions CI/CD is a legitimate automation migration, confirmed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions publish with SLSA attestation indicates a CI/CD pipeline change, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with org-level automation migration for the official Salesforce LWC monorepo. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 9.3.4 | 0 / 7 | |
| 9.2.2 | 0 / 7 | |
| 9.2.1 | 0 / 7 | |
| 9.2.0 | 0 / 7 | |
| 9.1.3 | 0 / 7 | |
| 9.1.2 | 0 / 7 | |
| 8.28.2 | 0 / 7 | |
| 8.28.1 | 0 / 7 | |
| 8.28.0 | 0 / 7 | |
| 8.27.0 | 0 / 7 | |
| 8.26.2 | 0 / 7 | |
| 8.26.1 | 0 / 7 | |
| 8.26.0 | 0 / 7 | |
| 8.25.1 | 0 / 7 | |
| 8.25.0 | 0 / 7 | |
| 8.24.0 | 0 / 7 |
v9.3.4
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.