← Home

@wemap/providers

npm

The positioning package provides location tracking and positioning capabilities using various location sources.

8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

wemap

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-lived @wemap org package with 331 versions; minor patch with no material changes, low takeover risk. ai
dependencies unvetted-dep:@wemap/utils AI (dependencies): Same-org scoped dependency (@wemap/utils) pinned to matching version; stable pattern across this monorepo. ai
phantom-deps phantom-dep:@wemap/osm AI (phantom-deps): Same-org monorepo dep; declared but may be re-exported rather than directly imported. ai
phantom-deps phantom-dep:@wemap/core AI (phantom-deps): Same-org monorepo dep; declared but may be re-exported rather than directly imported. ai

Versions (showing 8 of 8)

Version Deps Published
14.5.2 6 / 3
14.5.1 6 / 3
14.5.0 6 / 3
14.4.0 6 / 3
14.3.1 6 / 3
14.3.0 6 / 3
14.2.0 6 / 3
14.1.0 3 / 6

v14.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.