@classytic/invoice
Country-agnostic invoice engine for MongoDB — invoices, bills, credit notes, receipts, aging, payments
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): classytic-bot has strong track record (92 approved) across classytic packages; org-internal automation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same bot account transition, consistent with org's publishing automation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 0 / 14 | |
| 0.7.0 | 0 / 14 | |
| 0.6.2 | 0 / 14 | |
| 0.6.1 | 0 / 14 | |
| 0.6.0 | 0 / 14 | |
| 0.5.1 | 0 / 14 | |
| 0.5.0 | 0 / 14 | |
| 0.4.0 | 0 / 14 | |
| 0.3.0 | 0 / 14 | |
| 0.2.0 | 0 / 14 | |
| 0.1.2 | 0 / 14 | |
| 0.1.1 | 0 / 14 | |
| 0.1.0 | 0 / 13 |
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-29. 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.0
1 findingPackage 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.