← Home

@gem-sdk/adapter-bigcommerce

npm
6
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

gemcommerceharry.gem

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal SDK adapter in a large monorepo; missing metadata is a stable pattern across all @gem-sdk/* packages. ai
npm-metadata no-description AI (npm-metadata): Consistent with @gem-sdk/* internal adapter pattern; not indicative of malice. ai

Versions (showing 6 of 6)

Version Deps Published
16.0.0 0 / 1
13.1.5 0 / 1
13.1.0 0 / 1
13.0.0 0 / 1
11.2.0 0 / 1
7.0.0 0 / 1

v13.1.5

1 finding
LOW No provenance attestation provenance

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

v13.1.0

1 finding
LOW No provenance attestation provenance

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

v13.0.0

1 finding
LOW No provenance attestation provenance

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

v11.2.0

1 finding
LOW No provenance attestation provenance

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

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