@splunk/visualization-schemas
This package publishes the optionSchema for viz components published in @splunk/visualizations package.
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:@types/json-schema | AI (phantom-deps): Type-only dependency; not imported at runtime, stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Splunk internal package; sparse metadata is expected for org-internal tooling, not a spam indicator. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 28.7.0 | 2 / 2 | |
| 28.6.0 | 2 / 2 | |
| 28.4.0 | 2 / 2 | |
| 28.3.0 | 2 / 2 | |
| 28.2.3 | 2 / 2 | |
| 28.2.2 | 2 / 2 | |
| 28.2.1 | 2 / 2 | |
| 28.2.0 | 2 / 2 | |
| 28.1.0 | 2 / 2 | |
| 28.0.0 | 2 / 2 | |
| 27.2.3 | 1 / 4 | |
| 27.2.2 | 1 / 4 |
v28.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 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. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Consider requesting the maintainer enable provenance via CI/CD.