← Home

@epam/statgpt-sdmx-toolkit

npm

This is StatGpt portals library offers tools and utilities for working with SDMX (Statistical Data and Metadata eXchange) data formats and Api in the StatGPT portal frontend. It includes parsing, validation, and integration logic for SDMX structures and u

15
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

statgpt-actions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@epam/statgpt-dial-toolkit AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in source. ai
phantom-deps phantom-dep:@epam/statgpt-shared-toolkit AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in source. ai
phantom-deps phantom-dep:date-fns AI (phantom-deps): Declared in config files; stable false positive for this package. ai
phantom-deps phantom-dep:compare-versions AI (phantom-deps): Declared in config files; stable false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.6.0 4 / 0
0.5.0 4 / 0
0.4.3 4 / 0
0.4.2 4 / 0
0.4.1 4 / 0
0.4.0 4 / 0
0.3.4 4 / 0
0.3.3 4 / 0
0.3.2 4 / 0
0.3.1 4 / 0
0.3.0 4 / 0
0.2.0 3 / 0
0.1.2 3 / 0
0.1.1 3 / 0
0.1.0 3 / 0

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.