← Home

evalguardai-sdk

npm Repository Homepage

DEPRECATED — install '@evalguard/sdk' instead. This package is a thin re-export shim kept so existing installs keep working; the canonical name is @evalguard/sdk.

7
Versions
Apache-2.0
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

barathkumargopi

Keywords

deprecatedevalguardevalguard-sdk@evalguard/sdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Common for small packages; no other risk signals. ai
semgrep semgrep:child-process-import AI (semgrep): Used in CLI binary to delegate to sub-process; expected pattern for a CLI wrapper tool. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.0 1 / 0
1.2.0 2 / 2
1.1.0 2 / 2
1.0.3 2 / 2
1.0.2 2 / 2
1.0.1 2 / 2
1.0.0 1 / 3

v2.0.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.

v1.2.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.

v1.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.

v1.0.3

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.

v1.0.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.

v1.0.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.

v1.0.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.