@epicdm/flowstate-finance-core
Canonical journal-entry types and balance utilities shared across FlowState finance consumers. Phase 1 ships types + calculations; the posting engine, mapping resolver, and orchestrator land in subsequent phases (see docs/specs/2026-05-02-flowstate-financ
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 0 / 9 | |
| 0.1.6 | 0 / 9 | |
| 0.1.5 | 0 / 9 | |
| 0.1.4 | 0 / 9 | |
| 0.1.3 | 0 / 9 | |
| 0.1.2 | 0 / 9 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 |
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.