@epam/statgpt-conversation-view
This is StatGpt portals library, provides reusable React components, context, and utilities for managing and displaying advanced conversation views within the StatGPT portals. It includes logic for representing conversations, chating, handling stream-mess
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
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.6.1 | 24 / 0 | |
| 0.6.0 | 24 / 0 | |
| 0.5.0 | 24 / 0 | |
| 0.4.3 | 24 / 0 | |
| 0.4.2 | 24 / 0 | |
| 0.4.1 | 24 / 0 | |
| 0.4.0 | 24 / 0 | |
| 0.3.4 | 23 / 0 | |
| 0.3.3 | 23 / 0 | |
| 0.3.2 | 23 / 0 | |
| 0.3.1 | 23 / 0 | |
| 0.3.0 | 23 / 0 | |
| 0.2.0 | 23 / 0 | |
| 0.1.2 | 22 / 0 | |
| 0.1.1 | 22 / 0 | |
| 0.1.0 | 22 / 0 |
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.