@classytic/ledger-ca
Canada country pack for @classytic/ledger — GIFI chart of accounts, GST/HST/PST/QST tax codes, CRA return
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 within same org, consistent with automated release pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same org bot maintainer added; not a compromise indicator here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 0 / 14 | |
| 0.3.1 | 0 / 14 | |
| 0.3.0 | 0 / 12 | |
| 0.2.0 | 0 / 5 | |
| 0.1.4 | 0 / 5 | |
| 0.1.3 | 0 / 5 | |
| 0.1.2 | 0 / 5 |
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. 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.3.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-05-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.0
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-05-10. This could indicate a legitimate maintainer transition or an account compromise.