@classytic/cart
Framework-agnostic universal cart engine for commerce — drafts, checkouts, reservations, the LineKind strategy, and a disciplined finalization saga. Powered by MongoDB via @classytic/mongokit. Zero framework deps — usable from Arc, Express, Nest, Next.js,
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Bot-account maintainer transition with strong track record; no behavior change observed. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Corresponds to same bot-account transition, benign. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @classytic/cart is a cart engine; Levenshtein match to 'cors' is coincidental and not a typosquat. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 0 / 13 | |
| 0.2.1 | 0 / 13 | |
| 0.2.0 | 0 / 13 | |
| 0.1.3 | 0 / 13 | |
| 0.1.2 | 0 / 12 | |
| 0.1.1 | 0 / 12 | |
| 0.1.0 | 0 / 11 |
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.