@panneau/field-select
A select field
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped babel runtime; stable false positive for this build-tool-heavy package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; no provenance is consistent across all 409 versions, not a new concern. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types declared dep used transitively; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is a declared runtime dep used via build tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@panneau/themes | AI (phantom-deps): Same-org scoped package declared in dependencies; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 4.0.55 | 8 / 2 | |
| 4.0.50 | 8 / 2 | |
| 4.0.48 | 8 / 2 | |
| 4.0.41 | 8 / 2 | |
| 4.0.39 | 8 / 2 | |
| 4.0.38 | 8 / 2 | |
| 4.0.37 | 8 / 2 | |
| 4.0.36 | 8 / 2 | |
| 4.0.34 | 8 / 2 | |
| 4.0.33 | 8 / 2 | |
| 4.0.28 | 8 / 2 | |
| 4.0.27 | 8 / 2 | |
| 4.0.21 | 8 / 2 | |
| 4.0.20 | 8 / 2 | |
| 4.0.19 | 8 / 2 | |
| 4.0.18 | 8 / 2 | |
| 4.0.17 | 8 / 2 | |
| 4.0.15 | 8 / 2 | |
| 4.0.14 | 8 / 2 | |
| 4.0.11 | 9 / 2 | |
| 4.0.8 | 9 / 2 | |
| 4.0.7 | 9 / 2 | |
| 4.0.6 | 9 / 2 | |
| 4.0.5 | 9 / 2 | |
| 4.0.4 | 9 / 2 | |
| 4.0.2 | 9 / 2 | |
| 4.0.1 | 9 / 2 | |
| 4.0.0 | 9 / 2 | |
| 3.0.319 | 9 / 2 | |
| 3.0.317 | 9 / 2 | |
| 3.0.314 | 9 / 2 | |
| 3.0.311 | 9 / 2 | |
| 3.0.310 | 9 / 2 | |
| 3.0.308 | 9 / 2 | |
| 3.0.307 | 9 / 2 |
v4.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dmongeau) than the most recent previously approved version (phatshambler) on 2026-04-29, but dmongeau 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.
v4.0.37
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dmongeau) than the most recent previously approved version (phatshambler) on 2026-04-29, but dmongeau 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.
v4.0.36
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dmongeau) than the most recent previously approved version (phatshambler) on 2026-04-29, but dmongeau 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.
v4.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.317
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.314
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.