@opengeoweb/form-fields
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:lodash | AI (phantom-deps): Component library; peer/config-level dep pattern, stable across versions. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): i18n framework dep used via config convention, stable for this package. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): MUI is a declared dep used via re-exports/config; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): i18n framework dep used via config convention, stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Type-only package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Form library dep used via config/re-export pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/theme | AI (phantom-deps): Same-org sibling dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opengeoweb/shared | AI (phantom-deps): Same-org sibling dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mui/x-date-pickers | AI (phantom-deps): MUI date pickers declared dep; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Thin README and tiny payload are consistent with a monorepo sub-package; not spam. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 18.0.0 | 9 / 1 | |
| 17.2.0 | 9 / 1 | |
| 17.1.0 | 9 / 1 | |
| 17.0.1 | 9 / 1 | |
| 17.0.0 | 9 / 1 | |
| 15.2.0 | 9 / 1 | |
| 15.1.0 | 9 / 1 | |
| 15.0.0 | 9 / 1 | |
| 14.4.0 | 9 / 1 | |
| 14.3.0 | 9 / 1 | |
| 14.2.2 | 9 / 1 | |
| 14.2.1 | 9 / 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 (karoliinahautala) on unknown date, 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.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-19. 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.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. 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.
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. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.