@wireio/shared-web
Web-specific shared utilities for Wire applications. Extends `@wireio/shared` with browser-targeted functionality.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wireio/shared | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported. Stable FP for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.0.74 | 1 / 3 | |
| 1.0.73 | 1 / 3 | |
| 1.0.72 | 1 / 3 | |
| 1.0.71 | 1 / 3 | |
| 1.0.70 | 1 / 3 | |
| 1.0.69 | 1 / 3 | |
| 1.0.68 | 1 / 3 | |
| 1.0.67 | 1 / 3 | |
| 1.0.66 | 1 / 3 | |
| 1.0.65 | 1 / 3 | |
| 1.0.62 | 1 / 3 | |
| 1.0.61 | 1 / 3 | |
| 1.0.60 | 1 / 3 | |
| 1.0.59 | 1 / 3 | |
| 1.0.58 | 1 / 3 | |
| 1.0.57 | 1 / 3 | |
| 1.0.56 | 1 / 3 | |
| 1.0.55 | 1 / 3 | |
| 1.0.54 | 1 / 3 | |
| 1.0.53 | 1 / 3 | |
| 1.0.52 | 1 / 3 | |
| 1.0.51 | 1 / 3 | |
| 1.0.50 | 1 / 3 | |
| 1.0.49 | 1 / 3 | |
| 1.0.48 | 1 / 3 | |
| 1.0.47 | 1 / 3 | |
| 1.0.46 | 1 / 3 | |
| 1.0.45 | 1 / 3 | |
| 1.0.44 | 1 / 3 | |
| 1.0.43 | 1 / 3 | |
| 1.0.42 | 1 / 3 | |
| 1.0.41 | 1 / 3 | |
| 1.0.40 | 1 / 3 | |
| 1.0.36 | 1 / 3 | |
| 1.0.35 | 1 / 3 | |
| 1.0.34 | 1 / 3 | |
| 1.0.33 | 1 / 3 | |
| 1.0.32 | 1 / 3 | |
| 1.0.31 | 1 / 3 | |
| 1.0.27 | 1 / 3 | |
| 1.0.26 | 1 / 3 | |
| 1.0.25 | 1 / 3 | |
| 1.0.24 | 1 / 3 | |
| 1.0.23 | 1 / 3 |
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
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 (jglanz) than the most recent previously approved version (wn-user) on 2026-07-17, but jglanz 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.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.