@splunk/react-field-summary
This component creates a field summary list container which categorizes the fields that are present in the events/results that are returned from a search job. The fields can be categorized and/or sorted in any way the consumer of this component chooses.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): First-party Splunk dependency; consistent with this package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): First-party Splunk dependency; consistent with this package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): First-party Splunk dependency; consistent with this package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): First-party Splunk dependency; consistent with this package's ecosystem context. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types declared as runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped babel runtime; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 28.6.0 | 6 / 33 | |
| 28.5.3 | 6 / 33 | |
| 28.5.2 | 6 / 33 | |
| 28.5.1 | 6 / 33 | |
| 28.5.0 | 6 / 33 | |
| 28.4.0 | 6 / 33 | |
| 28.3.0 | 6 / 33 | |
| 28.2.3 | 6 / 33 | |
| 28.2.2 | 6 / 33 | |
| 28.2.1 | 6 / 33 | |
| 28.2.0 | 6 / 33 | |
| 28.1.0 | 6 / 35 | |
| 28.0.0 | 6 / 35 | |
| 27.5.2 | 6 / 41 | |
| 27.5.1 | 6 / 41 | |
| 27.2.3 | 6 / 34 | |
| 27.2.2 | 6 / 34 |
v28.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.