@classytic/loyalty
Loyalty points, tiers, earning rules, referrals, and redemption engine for MongoDB
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 transition for CI release automation, strong prior approval track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same bot maintainer addition tied to publisher-changed event. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 0 / 14 | |
| 0.4.0 | 0 / 14 | |
| 0.3.0 | 0 / 14 | |
| 0.2.3 | 0 / 14 | |
| 0.2.2 | 0 / 14 | |
| 0.2.1 | 0 / 14 | |
| 0.2.0 | 0 / 13 | |
| 0.1.0 | 0 / 10 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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.2.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-29. This could indicate a legitimate maintainer transition or an account compromise.