@bimetal/gantt-data
Gantt-domain event-sourcing: Chart-as-Aggregate (Tasks + Dependency-Kanten sind EIN Aggregat mit harten Invarianten — Finish-to-Start-Constraint, Zyklenfreiheit). Commands/events, ganttAggregate, ganttProjection, createGanttStore. Built on @bimetal/event-
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@bimetal/temporal | AI (dependencies): Same-org sibling package within bimetal monorepo, not third-party. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.35.0 | 2 / 1 | |
| 0.34.0 | 2 / 1 | |
| 0.32.0 | 2 / 1 | |
| 0.30.0 | 2 / 1 | |
| 0.29.0 | 2 / 1 |
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.