@wemap/geo
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 8 approved packages and this version shows no material changes vs prior approved release. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is a stable pattern across @wemap scope. | ai | |
| provenance | no-provenance | AI (provenance): Established @wemap org package; no provenance is consistent across their releases. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @wemap org package with 167 versions; not a typosquat of glob. | ai | |
| phantom-deps | phantom-dep:@wemap/utils | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for intra-org scoped packages. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @wemap org package with 167 versions; not a typosquat of got. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package published publicly; sparse metadata is consistent across all 167 versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 14.5.4 | 2 / 4 | |
| 14.5.2 | 2 / 4 | |
| 14.5.1 | 2 / 4 | |
| 14.5.0 | 2 / 4 | |
| 14.4.0 | 2 / 4 | |
| 14.3.1 | 2 / 4 | |
| 14.3.0 | 2 / 4 | |
| 14.2.0 | 2 / 4 |
v14.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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.