@lwc/rollup-plugin
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): Salesforce LWC migrated to GitHub Actions CI/CD publishing with SLSA attestation; stable pattern going forward. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived Salesforce monorepo package; dormancy followed by CI/CD migration is expected, not suspicious. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with org-level CI/CD takeover of publishing; backed by SLSA provenance from salesforce/lwc repo. | ai | |
| dependencies | unvetted-dep:@lwc/compiler | AI (dependencies): Sibling LWC monorepo package published at the same version; stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 9.3.4 | 4 / 1 | |
| 9.2.2 | 4 / 1 | |
| 9.2.1 | 4 / 1 | |
| 9.2.0 | 4 / 1 | |
| 9.1.5 | 4 / 1 | |
| 9.1.4 | 4 / 1 | |
| 9.1.3 | 4 / 1 | |
| 9.1.2 | 4 / 1 | |
| 9.1.1 | 4 / 1 | |
| 9.1.0 | 4 / 1 | |
| 9.0.3 | 4 / 1 | |
| 9.0.2 | 4 / 1 | |
| 9.0.1 | 4 / 1 | |
| 9.0.0 | 4 / 1 | |
| 8.28.2 | 4 / 1 | |
| 8.28.1 | 4 / 1 | |
| 8.28.0 | 4 / 1 | |
| 8.27.0 | 4 / 1 | |
| 8.26.2 | 4 / 1 | |
| 8.26.1 | 4 / 1 | |
| 8.26.0 | 4 / 1 | |
| 8.25.1 | 4 / 1 | |
| 8.25.0 | 4 / 1 | |
| 8.24.0 | 4 / 1 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
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.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.