@harnessio/react-sei-panorama-service-client
Harness React sei panorama service client - SEI Panorama APIs integrated with react hooks for Panorama project
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): Package is a generated API client; new service endpoints routinely add many source files. | ai |
Versions (showing 51 of 137)
| Version | Deps | Published |
|---|---|---|
| 0.31.0 | 0 / 0 | |
| 0.30.1 | 0 / 0 | |
| 0.30.0 | 0 / 0 | |
| 0.29.0 | 0 / 0 | |
| 0.28.0 | 0 / 0 | |
| 0.27.0 | 0 / 0 | |
| 0.26.17 | 0 / 0 | |
| 0.26.16 | 0 / 0 | |
| 0.26.15 | 0 / 0 | |
| 0.26.14 | 0 / 0 | |
| 0.26.13 | 0 / 0 | |
| 0.26.12 | 0 / 0 | |
| 0.26.11 | 0 / 0 | |
| 0.26.10 | 0 / 0 | |
| 0.26.9 | 0 / 0 | |
| 0.26.8 | 0 / 0 | |
| 0.26.7 | 0 / 0 | |
| 0.26.6 | 0 / 0 | |
| 0.26.5 | 0 / 0 | |
| 0.26.4 | 0 / 0 | |
| 0.26.3 | 0 / 0 | |
| 0.26.2 | 0 / 0 | |
| 0.26.1 | 0 / 0 | |
| 0.26.0 | 0 / 0 | |
| 0.25.27 | 0 / 0 | |
| 0.25.26 | 0 / 0 | |
| 0.25.25 | 0 / 0 | |
| 0.25.24 | 0 / 0 | |
| 0.25.23 | 0 / 0 | |
| 0.25.22 | 0 / 0 | |
| 0.25.21 | 0 / 0 | |
| 0.25.20 | 0 / 0 | |
| 0.25.19 | 0 / 0 | |
| 0.25.18 | 0 / 0 | |
| 0.25.17 | 0 / 0 | |
| 0.25.16 | 0 / 0 | |
| 0.25.15 | 0 / 0 | |
| 0.25.14 | 0 / 0 | |
| 0.25.13 | 0 / 0 | |
| 0.25.12 | 0 / 0 | |
| 0.25.11 | 0 / 0 | |
| 0.25.9 | 0 / 0 | |
| 0.25.8 | 0 / 0 | |
| 0.25.7 | 0 / 0 | |
| 0.25.6 | 0 / 0 | |
| 0.25.5 | 0 / 0 | |
| 0.25.4 | 0 / 0 | |
| 0.25.3 | 0 / 0 | |
| 0.25.2 | 0 / 0 | |
| 0.25.1 | 0 / 0 | |
| 0.25.0 | 0 / 0 |
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.