← Home

@classytic/ledger

npm Repository Homepage

Production-grade double-entry accounting engine for MongoDB — schemas, reports, tax, multi-tenant

31
Versions
MIT
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

siam923classytic-bot

Keywords

accountingdouble-entrybookkeepingledgerjournalchart-of-accountsfinancial-reportsbalance-sheetincome-statementtrial-balancegeneral-ledgertaxgsthstvatmulti-tenantmongodbmongoosetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): classytic-bot is the org's CI bot with 82 approved packages; publisher change reflects org automation, not compromise. ai

Versions (showing 31 of 31)

Version Deps Published
0.17.0 0 / 14
0.16.0 0 / 14
0.15.2 0 / 14
0.15.1 0 / 14
0.15.0 0 / 14
0.13.0 0 / 14
0.12.5 0 / 14
0.12.4 0 / 14
0.12.3 0 / 14
0.12.2 0 / 14
0.12.1 0 / 14
0.12.0 0 / 14
0.11.0 0 / 14
0.10.3 0 / 15
0.10.2 0 / 15
0.10.1 0 / 14
0.10.0 0 / 14
0.9.1 0 / 11
0.9.0 0 / 11
0.8.0 0 / 11
0.7.0 0 / 10
0.6.0 0 / 10
0.5.1 0 / 10
0.5.0 0 / 10
0.4.2 0 / 10
0.4.1 0 / 10
0.4.0 0 / 10
0.3.0 0 / 7
0.2.0 0 / 7
0.1.5 0 / 7
0.1.3 0 / 7

v0.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

2 findings
HIGH Publisher changed: siam923 → classytic-bot (on 2026-07-04) provenance

This version was published by a different npm account than previous versions on 2026-07-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: siam923 → classytic-bot (on 2026-04-29) provenance

[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.

v0.10.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: siam923 → classytic-bot (on 2026-04-28) provenance

[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.