@splunk/react-events-viewer
This component provides the Events Viewer with the options to select your display style and configuration options like pagination and number of events.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Splunk internal publishing pipeline; lack of Sigstore provenance is consistent across their packages. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): Internal Splunk ecosystem dependency; consistent with this package's established Splunk origin. | ai | |
| dependencies | unvetted-dep:@splunk/splunk-utils | AI (dependencies): Internal Splunk ecosystem dependency; consistent with this package's established Splunk origin. | ai | |
| dependencies | unvetted-dep:@splunk/moment | AI (dependencies): Internal Splunk ecosystem dependency; consistent with this package's established Splunk origin. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): Internal Splunk ecosystem dependency; consistent with this package's established Splunk origin. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): Internal Splunk ecosystem dependency; consistent with this package's established Splunk origin. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk ecosystem dependency; consistent with this package's established Splunk origin. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel runtime; convention-loaded, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a declared runtime dep; phantom-dep heuristic fires as false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 28.6.0 | 9 / 38 | |
| 28.5.3 | 9 / 38 | |
| 28.5.2 | 9 / 38 | |
| 28.5.1 | 9 / 38 | |
| 28.5.0 | 9 / 38 | |
| 28.4.0 | 9 / 38 | |
| 28.3.0 | 9 / 38 | |
| 28.2.3 | 9 / 38 | |
| 28.2.2 | 9 / 38 | |
| 28.2.1 | 9 / 38 | |
| 28.2.0 | 9 / 38 | |
| 28.1.0 | 9 / 39 | |
| 28.0.0 | 9 / 39 | |
| 27.5.2 | 9 / 38 | |
| 27.5.1 | 9 / 38 | |
| 27.2.3 | 9 / 30 | |
| 27.2.2 | 9 / 30 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.