← Home

@premai/api-sdk

npm Repository Homepage

End-to-end encrypted OpenAI-compatible client with file upload and tools support, using XWing (ML-KEM768 + X25519) hybrid post-quantum encryption.

12
Versions
ISC
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

lorenzodalmazzofederico-prem

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:bare-fs AI (phantom-deps): bare-fs is used via package.json imports map as a Bare runtime polyfill for 'fs', not a direct import. ai
typosquat typosquat.levenshtein:aws-sdk AI (typosquat): @premai/api-sdk is a scoped SDK for the premai.io platform, not a typosquat of aws-sdk; Levenshtein match is coincidental. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript is a build-time dep legitimately listed; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:@noble/curves AI (phantom-deps): @noble/curves is used transitively via crypto stack; phantom detection is a false positive here. ai

Versions (showing 12 of 12)

Version Deps Published
1.0.42 23 / 6
1.0.41 19 / 6
1.0.40 19 / 6
1.0.39 19 / 6
1.0.38 19 / 6
1.0.37 19 / 6
1.0.36 19 / 6
1.0.35 19 / 6
1.0.32 19 / 6
1.0.31 13 / 6
1.0.30 13 / 6
1.0.29 13 / 6

v1.0.42

1 finding
LOW No provenance attestation provenance

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

v1.0.41

1 finding
LOW No provenance attestation provenance

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

v1.0.40

1 finding
LOW No provenance attestation provenance

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

v1.0.39

1 finding
LOW No provenance attestation provenance

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

v1.0.38

1 finding
LOW No provenance attestation provenance

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

v1.0.37

1 finding
LOW No provenance attestation provenance

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

v1.0.36

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

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

1 finding
LOW No provenance attestation provenance

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

v1.0.31

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

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

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.