← Home

@opengis/partsmap

npm

partsmap-plugins

18
Versions
ISC
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

evheniihavryliukandrii.cherinsetebosurapax.deusmchernenkoserebasikkartem_maniakinaponaskofarizov_maximbohdana_usenko

Keywords

partsmapmaplibrevuemaptable

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@tabler/icons-webfont AI (phantom-deps): Referenced in config files per analyzer note; icon font loaded via CSS/config. ai
phantom-deps phantom-dep:@panzoom/panzoom AI (phantom-deps): Referenced in config files per analyzer note; consistent with bundled component pattern. ai
phantom-deps phantom-dep:@opengis/v3-filter AI (phantom-deps): Same org scope; expected peer/re-export pattern. ai
phantom-deps phantom-dep:axios AI (phantom-deps): Bundled Vue component; deps may be used in config/runtime without direct ESM import. ai
phantom-deps phantom-dep:@turf/turf AI (phantom-deps): Same pattern — referenced in config files per analyzer note. ai
phantom-deps phantom-dep:maplibre-gl AI (phantom-deps): Core GIS dep; referenced in config files per analyzer note. ai
phantom-deps phantom-dep:@opengis/v3-core AI (phantom-deps): Same org scope; expected peer/re-export pattern. ai
phantom-deps phantom-dep:@opengis/filter AI (phantom-deps): Same org scope; likely used transitively or via peer resolution in this monorepo-style package. ai
phantom-deps phantom-dep:@opengis/core AI (phantom-deps): Same org scope; likely used transitively or via peer resolution in this monorepo-style package. ai

Versions (showing 18 of 18)

Version Deps Published
0.1.31 2 / 13
0.1.27 2 / 13
0.1.26 2 / 13
0.1.13 1 / 13
0.1.12 1 / 13
0.1.11 1 / 13
0.1.10 1 / 13
0.1.9 1 / 13
0.1.8 1 / 13
0.1.7 1 / 13
0.1.6 1 / 13
0.1.5 0 / 0
0.1.4 0 / 0
0.1.3 0 / 0
0.1.2 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.101 8 / 9

v0.1.27

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.

v0.1.26

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.

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

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.

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.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.

v0.0.101

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.