@opengeoweb/cap
GeoWeb Common Alerting Protocol (CAP) library for the opengeoweb project
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:@opengeoweb/webmap-react | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@reduxjs/toolkit | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/store | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/shared | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/webmap | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/time-slider | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ol | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@mui/system | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): Config-referenced indirect import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/api | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/core | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:frappe-gantt | AI (phantom-deps): frappe-gantt is a declared dep used in config files; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/theme | AI (phantom-deps): Same-org package; phantom-dep is a stable false positive for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package with 95 versions and clear description; sparse README/keywords are cosmetic, not spam indicators. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @opengeoweb package; Levenshtein match to 'yup' is a false positive with no plausible impersonation. | ai | |
| dependencies | unvetted-dep:@opengeoweb/store | AI (dependencies): Sibling monorepo package at matching version; not an external unvetted dependency. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @opengeoweb package; Levenshtein match to 'hapi' is a false positive with no plausible impersonation. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 18.0.0 | 17 / 1 | |
| 17.3.0 | 17 / 1 | |
| 17.2.0 | 17 / 1 | |
| 17.1.0 | 17 / 1 | |
| 17.0.1 | 17 / 1 | |
| 17.0.0 | 17 / 1 | |
| 16.0.0 | 17 / 1 | |
| 15.3.0 | 17 / 1 | |
| 15.2.0 | 17 / 1 | |
| 15.1.0 | 17 / 1 | |
| 15.0.0 | 17 / 1 | |
| 14.5.2 | 17 / 1 | |
| 14.5.1 | 17 / 1 | |
| 14.5.0 | 17 / 1 | |
| 14.4.0 | 17 / 1 | |
| 14.3.0 | 17 / 1 | |
| 14.2.2 | 17 / 1 | |
| 14.2.1 | 17 / 1 |
v18.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oyvindim) than the most recent previously approved version (mizzi_knmi) on 2026-05-28, but oyvindim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v17.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (maartenplieger) than the most recent previously approved version (esalie) on 2026-05-13, but maartenplieger is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v17.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karoliinahautala) than the most recent previously approved version (esalie) on 2026-04-29, but karoliinahautala is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v17.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karricgi) than the most recent previously approved version (esalie) on 2026-04-16, but karricgi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v17.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mizzi_knmi) than the most recent previously approved version (esalie) on 2026-04-08, but mizzi_knmi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v17.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (onetrium) than the most recent previously approved version (henrikj_) on 2026-01-22, but onetrium is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mizzi_knmi) than the most recent previously approved version (ernstdevreede) on 2026-01-08, but mizzi_knmi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v14.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.