@viasat/beam-react
React component library for the Beam design system
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known maintainer manual publish; matches audit trail, no behavior change. | ai | |
| provenance | publisher-changed-known-maintainer | AI (provenance): Publisher matched as known maintainer on prior approved versions. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-react-claude-plugin | AI (phantom-deps): Same-org scope; likely referenced via non-scanned config/build path. | ai | |
| dependencies | unvetted-dep:@viasat/beam-react-claude-plugin | AI (dependencies): Same-org scoped package, version-pinned in lockstep with monorepo siblings. | ai | |
| source-diff | obfuscated-file:chunks/Avatar.Bmy3T_0v.js | AI (source-diff): Bundled chunk output, not obfuscation. | ai | |
| source-diff | obfuscated-file:chunks/ActionList.Item.BAc--NcK.js | AI (source-diff): Rollup/Vite bundled chunk output, not obfuscation. | ai | |
| source-diff | obfuscated-file:chunks/SpinnerWrap.RW7jgvpb.js | AI (source-diff): Bundled chunk output, not obfuscation. | ai | |
| source-diff | obfuscated-file:chunks/form.context.D5XrYvpI.js | AI (source-diff): Bundled chunk output, not obfuscation. | ai | |
| source-diff | obfuscated-file:chunks/ActionList.Item.YxZyttjT.js | AI (source-diff): Minified Rollup chunk with readable React/CSS module content; standard build output for this design system library. | ai | |
| source-diff | obfuscated-file:chunks/FloatingUI.context.Du9g2lSg.js | AI (source-diff): Minified floating-ui logic chunk; readable algorithmic content, standard build output. | ai | |
| source-diff | obfuscated-file:chunks/form.context.hesWPMlU.js | AI (source-diff): Standard Rollup/Vite minified chunk; content is readable React form context code. | ai | |
| source-diff | obfuscated-file:chunks/ActionList.Item.Dk8VahiE.js | AI (source-diff): Standard Rollup/Vite minified chunk for a React component library; content is readable CSS class maps and JSX. | ai | |
| source-diff | obfuscated-file:chunks/Avatar.DL_F5o6f.js | AI (source-diff): Standard Rollup/Vite minified chunk; content is readable React component code. | ai | |
| source-diff | obfuscated-file:chunks/card.module.ZUNe5c82.js | AI (source-diff): Standard Rollup/Vite minified chunk; content is readable CSS class maps. | ai | |
| source-diff | obfuscated-file:chunks/SpinnerWrap.DGQJaMXI.js | AI (source-diff): Standard Rollup/Vite minified chunk; content is readable spinner component code. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Component library regularly adds new component source files across versions; pattern is expected for this package. | ai | |
| source-diff | obfuscated-file:chunks/card.module.BG9mkRao.js | AI (source-diff): File is a minified CSS module map with readable BEM class names; standard build artifact for this component library. | ai | |
| dependencies | unvetted-dep:@stepperize/react | AI (dependencies): Legitimate stepper/wizard UI utility; appropriate dependency for a React component library. | ai | |
| dependencies | unvetted-dep:@viasat/beam-fonts | AI (dependencies): Same org scope (@viasat); co-versioned sibling package, stable dependency for this library. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-fonts | AI (phantom-deps): Same-org sibling dep in a design system monorepo; not directly imported but re-exported as a bundled asset. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-icons | AI (phantom-deps): Same-org sibling dep in a design system monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:use-isomorphic-layout-effect | AI (phantom-deps): Referenced in config files; utility dep commonly used indirectly in component libraries. | ai | |
| phantom-deps | phantom-dep:next-themes | AI (phantom-deps): Referenced in config/type files; theme support dep pattern common in design systems. | ai | |
| phantom-deps | phantom-dep:@viasat/beam-styles | AI (phantom-deps): Same-org sibling dep in a design system monorepo; stable false positive. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 2.48.2 | 12 / 0 | |
| 2.48.0 | 12 / 0 | |
| 2.47.1 | 12 / 0 | |
| 2.47.0 | 12 / 0 | |
| 2.46.0 | 11 / 0 | |
| 2.45.1 | 11 / 0 | |
| 2.45.0 | 11 / 0 | |
| 2.44.0 | 11 / 0 | |
| 2.43.2 | 11 / 0 | |
| 2.43.1 | 11 / 0 | |
| 2.43.0 | 11 / 0 | |
| 2.42.0 | 11 / 0 | |
| 2.41.0 | 11 / 0 | |
| 2.40.0 | 11 / 0 | |
| 2.39.3 | 11 / 0 | |
| 2.39.2 | 11 / 0 | |
| 2.39.1 | 11 / 0 | |
| 2.39.0 | 11 / 0 | |
| 2.38.1 | 11 / 0 | |
| 2.38.0 | 11 / 0 | |
| 2.37.0 | 11 / 0 | |
| 2.36.0 | 11 / 0 | |
| 2.30.0 | 11 / 0 | |
| 2.29.1 | 11 / 0 | |
| 2.29.0 | 11 / 0 | |
| 2.28.0 | 11 / 0 | |
| 2.27.0 | 11 / 0 | |
| 2.26.1 | 11 / 0 | |
| 2.26.0 | 11 / 0 | |
| 2.25.0 | 11 / 0 | |
| 2.24.0 | 11 / 0 | |
| 2.23.0 | 11 / 0 | |
| 2.22.0 | 11 / 0 | |
| 2.21.1 | 11 / 0 | |
| 2.21.0 | 11 / 0 | |
| 2.20.0 | 11 / 0 | |
| 2.19.0 | 11 / 0 | |
| 2.18.1 | 11 / 0 | |
| 2.18.0 | 11 / 0 | |
| 2.17.0 | 11 / 0 | |
| 2.16.0 | 11 / 0 | |
| 2.15.0 | 11 / 0 | |
| 2.14.0 | 11 / 0 | |
| 2.13.0 | 11 / 0 | |
| 2.12.0 | 11 / 0 | |
| 2.11.0 | 11 / 0 | |
| 2.10.2 | 11 / 0 | |
| 2.10.1 | 11 / 0 | |
| 2.10.0 | 11 / 0 | |
| 2.9.0 | 11 / 0 | |
| 2.8.0 | 11 / 0 |
v2.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.46.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jevansvst.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jevansvst) than the most recent previously approved version (svc_pwaf-unpkg-artif) on 2026-06-17, but jevansvst is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.30.0
1 findingPackage 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.