@uniweb/kit
Standard component library for Uniweb foundations
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is from the same @uniweb namespace by the same trusted publisher; not an external supply-chain risk. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @uniweb package; not a plausible typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped @uniweb package; not a plausible typosquat of vite. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @uniweb package; not a plausible typosquat of got. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.9.15 | 6 / 1 | |
| 0.9.14 | 5 / 1 | |
| 0.9.13 | 5 / 1 | |
| 0.9.12 | 5 / 1 | |
| 0.9.11 | 5 / 1 | |
| 0.9.10 | 5 / 1 | |
| 0.9.9 | 5 / 1 | |
| 0.9.8 | 5 / 1 | |
| 0.9.7 | 5 / 1 | |
| 0.9.6 | 5 / 1 | |
| 0.9.5 | 5 / 1 | |
| 0.9.4 | 5 / 1 | |
| 0.9.3 | 5 / 1 | |
| 0.9.2 | 5 / 1 | |
| 0.9.1 | 5 / 1 | |
| 0.9.0 | 5 / 1 | |
| 0.8.3 | 5 / 1 | |
| 0.8.2 | 5 / 1 | |
| 0.8.1 | 5 / 1 | |
| 0.8.0 | 5 / 1 | |
| 0.7.24 | 5 / 1 | |
| 0.7.23 | 5 / 1 | |
| 0.7.22 | 5 / 1 | |
| 0.7.21 | 5 / 1 | |
| 0.7.20 | 5 / 1 | |
| 0.7.19 | 5 / 1 | |
| 0.7.18 | 5 / 1 | |
| 0.7.17 | 5 / 1 | |
| 0.7.16 | 5 / 1 | |
| 0.7.15 | 5 / 1 | |
| 0.7.14 | 5 / 1 | |
| 0.7.13 | 5 / 1 | |
| 0.7.12 | 5 / 1 | |
| 0.7.10 | 5 / 1 | |
| 0.7.9 | 5 / 1 | |
| 0.7.8 | 5 / 1 | |
| 0.7.7 | 5 / 1 | |
| 0.7.6 | 5 / 1 | |
| 0.7.5 | 4 / 1 | |
| 0.7.4 | 4 / 1 | |
| 0.7.3 | 4 / 1 | |
| 0.7.2 | 4 / 1 | |
| 0.7.1 | 4 / 1 | |
| 0.7.0 | 4 / 1 | |
| 0.6.1 | 4 / 1 | |
| 0.6.0 | 4 / 1 | |
| 0.5.12 | 4 / 1 | |
| 0.5.11 | 4 / 1 | |
| 0.5.10 | 4 / 1 | |
| 0.5.9 | 4 / 1 | |
| 0.5.8 | 4 / 1 |
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.