@operato/gantt
Webcomponents for gantt chart following open-wc recommendations
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Declared dependency used via @operato/i18n; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Declared dependency used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:d3-time-format | AI (phantom-deps): Declared dependency used indirectly; stable pattern for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.2.12 | 8 / 18 | |
| 9.1.0 | 8 / 18 | |
| 9.0.34 | 8 / 18 | |
| 9.0.21 | 8 / 18 | |
| 9.0.20 | 8 / 18 | |
| 9.0.1 | 8 / 18 | |
| 9.0.0 | 8 / 18 |
v9.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.