@wemap/osm
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @wemap org package; Levenshtein match to 'qs' is a false positive for scoped namespace packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Org-internal package with 216 versions and 6+ year history; sparse metadata is typical for internal libs. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 14.5.2 | 2 / 2 | |
| 14.5.1 | 2 / 2 | |
| 14.5.0 | 2 / 2 | |
| 14.4.0 | 2 / 2 | |
| 14.3.1 | 2 / 2 | |
| 14.3.0 | 2 / 2 | |
| 14.2.0 | 2 / 2 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.