@brandup/ui-website
Front-end website infrastructure.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@brandup/ui | AI (dependencies): Same-org sibling package; expected dependency for this scoped UI framework family. | ai | |
| dependencies | unvetted-dep:@brandup/ui-app | AI (dependencies): Same-org sibling package; expected dependency for this scoped UI framework family. | ai | |
| dependencies | unvetted-dep:@brandup/ui-dom | AI (dependencies): Same-org sibling package; expected dependency for this scoped UI framework family. | ai | |
| dependencies | unvetted-dep:@brandup/ui-ajax | AI (dependencies): Same-org sibling package; expected dependency for this scoped UI framework family. | ai | |
| dependencies | unvetted-dep:@brandup/ui-helpers | AI (dependencies): Same-org sibling package; expected dependency for this scoped UI framework family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is typical for this publisher/package family; not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 10.0.26 | 5 / 0 | |
| 10.0.25 | 5 / 0 | |
| 10.0.24 | 5 / 0 | |
| 10.0.19 | 5 / 0 | |
| 10.0.8 | 5 / 0 | |
| 10.0.5 | 5 / 0 | |
| 10.0.4 | 5 / 0 |
v10.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.