@uniweb/core
Core classes for the Uniweb platform - Uniweb, Website, Page, Block
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @uniweb/core package with 75 versions and official GitHub repo; not a typosquat of cors. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 0.7.33 | 2 / 1 | |
| 0.7.31 | 2 / 1 | |
| 0.7.30 | 2 / 1 | |
| 0.7.29 | 2 / 1 | |
| 0.7.28 | 2 / 1 | |
| 0.7.27 | 2 / 1 | |
| 0.7.26 | 2 / 1 | |
| 0.7.25 | 2 / 1 | |
| 0.7.24 | 2 / 1 | |
| 0.7.23 | 2 / 1 | |
| 0.7.22 | 2 / 1 | |
| 0.7.21 | 2 / 1 | |
| 0.7.20 | 2 / 1 | |
| 0.7.19 | 2 / 1 | |
| 0.7.18 | 2 / 1 | |
| 0.7.17 | 2 / 1 | |
| 0.7.16 | 2 / 1 | |
| 0.7.15 | 2 / 1 | |
| 0.7.14 | 2 / 1 | |
| 0.7.13 | 2 / 1 | |
| 0.7.12 | 2 / 1 | |
| 0.7.11 | 2 / 1 | |
| 0.7.8 | 2 / 1 | |
| 0.5.22 | 2 / 1 | |
| 0.5.21 | 2 / 1 | |
| 0.5.20 | 2 / 1 | |
| 0.5.19 | 2 / 1 | |
| 0.5.18 | 2 / 1 | |
| 0.5.17 | 2 / 1 | |
| 0.5.16 | 2 / 1 | |
| 0.5.15 | 2 / 1 | |
| 0.5.14 | 2 / 1 | |
| 0.5.13 | 2 / 1 | |
| 0.5.12 | 2 / 1 | |
| 0.5.11 | 2 / 1 | |
| 0.5.10 | 1 / 1 | |
| 0.5.9 | 1 / 1 | |
| 0.5.8 | 1 / 1 | |
| 0.5.7 | 1 / 1 | |
| 0.5.6 | 1 / 1 | |
| 0.5.5 | 1 / 1 | |
| 0.5.4 | 1 / 1 | |
| 0.5.3 | 1 / 1 | |
| 0.5.2 | 1 / 1 | |
| 0.5.1 | 1 / 1 | |
| 0.5.0 | 1 / 1 | |
| 0.4.8 | 1 / 1 | |
| 0.4.7 | 1 / 1 | |
| 0.4.6 | 1 / 1 | |
| 0.4.5 | 1 / 1 | |
| 0.4.4 | 1 / 1 |
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
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.20
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. Consider requesting the maintainer enable provenance via CI/CD.
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.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
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-06, 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.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
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.