← Home

@uniweb/build

Build tooling for the Uniweb Component Web Platform

100
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

wengtyttproximify

Keywords

uniwebfoundationsitebuildvitecomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@uniweb/projections AI (dependencies): First-party same-org dependency, part of the Uniweb build toolchain. ai
source-diff net-exec-file:src/hosts/s3-cloudfront.js AI (source-diff): Legitimate AWS deployment adapter; uses aws CLI via spawn and fs writes — documented build tool behavior, not malware. ai
publish-pattern new-deps-added AI (publish-pattern): js-yaml is a well-established package; addition is consistent with new YAML-handling features in expanded exports. ai
provenance missing-githead AI (provenance): Publisher has 121 approved packages; likely CI environment change, not a supply-chain indicator. ai
source-diff large-new-source-files AI (source-diff): 22 new files match the 8 new export subpaths added in this version; organic expansion. ai
source-diff source-size-tripled AI (source-diff): Size increase explained by new feature modules (foundation, site, dev, i18n, search, prerender subpaths). ai
provenance no-provenance AI (provenance): Established publisher with clean track record; provenance absence is a process gap, not a security signal for this package. ai
typosquat typosquat.levenshtein:esbuild AI (typosquat): Package actually depends on esbuild as a legitimate runtime dep; not a typosquat. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped @uniweb/build is an established build tool, not a typosquat of uuid; Levenshtein match is coincidental. ai

Versions (showing 100 of 203)

Version Deps Published
0.15.12 8 / 1
0.15.11 8 / 1
0.15.10 8 / 1
0.15.9 8 / 1
0.15.8 8 / 1
0.15.7 8 / 1
0.15.6 8 / 1
0.15.5 7 / 1
0.15.4 7 / 1
0.15.3 7 / 1
0.15.2 7 / 1
0.15.1 7 / 1
0.15.0 7 / 1
0.14.40 7 / 1
0.14.39 7 / 1
0.14.38 7 / 1
0.14.37 7 / 1
0.14.36 7 / 1
0.14.35 7 / 1
0.14.34 7 / 1
0.14.33 7 / 1
0.14.32 7 / 1
0.14.31 7 / 1
0.14.30 7 / 1
0.14.29 7 / 1
0.14.28 7 / 1
0.14.27 7 / 1
0.14.26 7 / 1
0.14.25 7 / 1
0.14.24 7 / 1
0.14.23 7 / 1
0.14.22 7 / 1
0.14.21 7 / 1
0.14.20 7 / 1
0.14.19 7 / 1
0.14.18 7 / 1
0.14.17 7 / 1
0.14.16 7 / 1
0.14.15 7 / 1
0.14.14 7 / 1
0.14.13 7 / 1
0.14.12 7 / 1
0.14.11 7 / 1
0.14.10 7 / 1
0.14.9 7 / 1
0.14.8 7 / 1
0.14.7 7 / 1
0.14.6 7 / 1
0.14.5 6 / 1
0.14.4 6 / 1
0.14.3 6 / 1
0.14.2 6 / 1
0.14.1 5 / 1
0.13.5 5 / 1
0.13.4 5 / 1
0.13.3 5 / 1
0.13.2 5 / 1
0.13.1 5 / 1
0.13.0 5 / 1
0.12.0 5 / 1
0.11.9 5 / 1
0.11.8 5 / 1
0.11.7 5 / 1
0.11.6 5 / 1
0.11.5 5 / 1
0.11.4 5 / 1
0.11.3 4 / 1
0.11.2 4 / 1
0.10.3 4 / 1
0.10.2 4 / 1
0.10.1 4 / 1
0.10.0 4 / 1
0.9.5 4 / 1
0.9.4 4 / 1
0.9.3 4 / 1
0.9.2 4 / 1
0.9.1 4 / 1
0.9.0 4 / 1
0.8.42 4 / 1
0.8.41 4 / 1
0.8.40 4 / 1
0.8.39 4 / 1
0.8.38 4 / 1
0.8.37 4 / 1
0.8.36 4 / 1
0.8.35 4 / 1
0.8.34 4 / 1
0.8.33 4 / 1
0.8.32 4 / 1
0.8.31 4 / 1
0.8.30 4 / 1
0.8.29 4 / 1
0.8.28 4 / 1
0.8.27 4 / 1
0.8.26 4 / 1
0.8.25 4 / 1
0.8.24 4 / 1
0.8.23 4 / 1
0.8.22 4 / 1
0.8.21 4 / 1
Showing 100 of 203 Next page →

v0.15.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.40

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.39

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.38

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.37

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.36

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.35

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.34

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: proximify → wengtytt (on 2026-04-21, known maintainer) provenance

This version was published by a different npm account (wengtytt) than the most recent previously approved version (proximify) on 2026-04-21, but wengtytt 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.

v0.10.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.41

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.40

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.37

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.35

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.34

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.