← Home

@storecraft/core

npm Repository Homepage

Core Package for storecraft

5
Versions
MIT (With special clause. You cannot sell storecraft or offer a cloud service based on it without a special license)
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

hendrixstring

Keywords

commercedashboardcodestorecraftstoreaiagentsshopping

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): @storecraft/core is a scoped e-commerce framework; not a typosquat of cors. ai
semgrep semgrep:base64-decode AI (semgrep): Standard base64 decode in crypto utility; no malicious payload pattern. ai
semgrep semgrep:new-function-constructor AI (semgrep): Used in minibars.js template engine for template compilation; expected pattern. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decode used in crypto/scrypt key handling; legitimate cryptographic use. ai

Versions (showing 5 of 5)

Version Deps Published
1.4.2 1 / 7
1.0.41 1 / 6
1.0.40 1 / 6
1.0.39 1 / 6
1.0.38 1 / 6

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.38

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.