@wemap/positioning
The positioning package provides location tracking and positioning capabilities using various location sources.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wemap/utils | AI (phantom-deps): Same-org scoped dep; likely re-exported rather than directly imported in this package. | ai | |
| phantom-deps | phantom-dep:@wemap/routers | AI (phantom-deps): Same-org scoped dep; likely re-exported rather than directly imported in this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 14.5.2 | 5 / 1 | |
| 14.5.1 | 5 / 1 | |
| 14.5.0 | 5 / 1 | |
| 14.4.0 | 5 / 1 | |
| 14.1.0 | 2 / 4 | |
| 14.0.0 | 1 / 5 |
v14.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.