@wemap/routers
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal @wemap org package; sparse metadata is consistent across 206 versions, not indicative of spam/malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable org-scoped package; missing description is a style issue, not a risk signal. | ai | |
| phantom-deps | phantom-dep:@wemap/core | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly via framework conventions. | ai | |
| phantom-deps | phantom-dep:@turf/convex | AI (phantom-deps): Analyzer notes it's referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@turf/helpers | AI (phantom-deps): Analyzer notes it's referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/mapbox__polyline | AI (phantom-deps): Type-only package loaded by convention; stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 14.5.2 | 9 / 8 | |
| 14.5.1 | 9 / 8 | |
| 14.5.0 | 9 / 8 | |
| 14.4.0 | 9 / 8 | |
| 14.3.0 | 9 / 8 | |
| 14.2.0 | 9 / 8 |
v14.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.