← Home

@unchainedshop/api

npm Repository Homepage

GraphQL API layer for the Unchained Engine with Express/Fastify adapters and MCP server

13
Versions
EUPL-1.2
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

kaufmaemikearaya

Keywords

unchainedecommerceapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:expiry-map AI (dependencies): expiry-map is a small, well-known utility; no advisories or malicious indicators. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package in established unchainedshop monorepo; not a typosquat of hapi. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package in established unchainedshop monorepo; not a typosquat of pg. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package in established unchainedshop monorepo; not a typosquat of joi. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package in established unchainedshop monorepo; not a typosquat of ajv. ai
semgrep semgrep:base64-decode AI (semgrep): Decodes WebAuthn userHandle per spec; standard protocol usage, not obfuscation. ai

Versions (showing 13 of 13)

Version Deps Published
4.8.13 11 / 16
4.8.12 11 / 16
4.8.11 11 / 16
4.8.9 11 / 16
4.8.4 11 / 16
4.7.2 12 / 14
4.6.0 11 / 16
4.3.2 12 / 19
4.2.2 12 / 18
4.1.2 12 / 18
4.1.1 12 / 18
4.0.1 12 / 17
4.0.0 12 / 17

v4.8.13

1 finding
LOW No provenance attestation provenance

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

v4.8.11

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.

v4.8.9

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.

v4.8.4

1 finding
LOW No provenance attestation provenance

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

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

v4.6.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.

v4.3.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.

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

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

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

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

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