@viasat/beam-web-components
Framework-agnostic web components for the Beam Design System built with Lit, compatible with Angular, Vue, Svelte, and vanilla JavaScript
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal Viasat design system package; provenance attestation not configured for this org's pipeline. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-fonts | AI (phantom-deps): Asset/font package; not directly imported in JS but used as a peer resource — stable false positive for this org. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-icons | AI (phantom-deps): Asset/icon package; same pattern as beam-fonts — stable false positive for this org. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-styles | AI (phantom-deps): CSS-only package; not directly imported in JS — stable false positive for this org. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-tokens | AI (phantom-deps): Design token package; not directly imported in JS — stable false positive for this org. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.29.1 | 10 / 0 | |
| 2.29.0 | 10 / 0 | |
| 2.27.0 | 10 / 0 | |
| 2.26.1 | 10 / 0 | |
| 2.26.0 | 10 / 0 | |
| 2.21.1 | 10 / 0 | |
| 2.18.0 | 10 / 0 | |
| 2.17.0 | 10 / 0 | |
| 2.14.0 | 10 / 0 | |
| 2.13.0 | 10 / 0 | |
| 2.10.2 | 10 / 0 | |
| 2.10.1 | 10 / 0 | |
| 2.10.0 | 10 / 0 | |
| 2.9.0 | 10 / 0 | |
| 2.2.0 | 10 / 0 |
v2.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.