@splunk/dashboard-inputs
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Large file count consistent with major version bump (28.x→29.5.1) adding new input components. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are @splunk org packages or well-known libs; consistent with a major version bump in a monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Splunk org packages consistently lack Sigstore provenance; not a risk indicator for this publisher. | ai | |
| phantom-deps | phantom-dep:memoize-one | AI (phantom-deps): Declared but not imported; likely a transitive or config-only reference, not a real risk for this package. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-ui | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/splunk-utils | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/react-time-range | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/time-range-utils | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-definition | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/moment | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): Internal Splunk org dependency; consistent pattern across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Splunk org package; sparse metadata is typical for internal monorepo packages. | ai | |
| phantom-deps | phantom-dep:@splunk/splunk-utils | AI (phantom-deps): Same-org dependency; likely used transitively within the Splunk ecosystem. | ai | |
| phantom-deps | phantom-dep:@splunk/moment | AI (phantom-deps): Same-org dependency; likely used transitively within the Splunk ecosystem. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 18 / 19 | |
| 29.5.1 | 18 / 19 | |
| 29.5.0 | 18 / 19 | |
| 29.4.0 | 17 / 19 | |
| 29.3.4 | 18 / 23 | |
| 29.3.3 | 18 / 23 | |
| 29.3.2 | 18 / 23 | |
| 29.3.1 | 18 / 23 | |
| 29.3.0 | 18 / 23 | |
| 29.2.1 | 18 / 23 | |
| 29.2.0 | 18 / 23 | |
| 29.1.0 | 19 / 23 | |
| 29.0.0 | 18 / 23 | |
| 28.6.3 | 18 / 21 | |
| 28.6.2 | 18 / 21 | |
| 28.2.2 | 18 / 21 |
v29.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.6.2
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.