@geolonia/maps-suite
High-level map components built on @geolonia/maps-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:maplibre-gl | AI (phantom-deps): Bundled output; maplibre-gl is bundled at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@geolonia/maps-core | AI (phantom-deps): Same-org dependency likely consumed via bundled output; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; provenance absence is common and no other risk signals present. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 1 / 17 | |
| 0.2.0 | 1 / 17 | |
| 0.1.2 | 1 / 17 | |
| 0.0.2 | 1 / 16 | |
| 0.0.1 | 2 / 13 |
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.