← Home

@svar-ui/react-gantt

npm Repository Homepage
12
Versions
—
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

marta-komkozhukh

Keywords

reactreactjsreact-componentreact-ganttgantt-reactganttgantt-chartreact-gantt-chartgantt-chart-componentgantt-diagramreact-gantt-componentsvar widgetssvar-reacttimelinetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:date-fns AI (phantom-deps): date-fns is a declared dep used in config/build context; stable false positive for this package. ai
phantom-deps phantom-dep:@svar-ui/react-filter AI (phantom-deps): Same-org dep; likely re-exported or indirectly used. Stable false positive. ai
phantom-deps phantom-dep:@svar-ui/react-comments AI (phantom-deps): Same-org dep; likely re-exported or indirectly used. Stable false positive. ai
phantom-deps phantom-dep:@svar-ui/react-tasklist AI (phantom-deps): Same-org dep; likely re-exported or indirectly used. Stable false positive. ai
phantom-deps phantom-dep:@svar-ui/gantt-data-provider AI (phantom-deps): Same-org dep; likely re-exported or indirectly used. Stable false positive. ai

Versions (showing 12 of 12)

Version Deps Published
2.7.1 17 / 16
2.7.0 17 / 16
2.6.1 12 / 15
2.6.0 12 / 15
2.5.2 11 / 15
2.4.5 11 / 15
2.4.4 11 / 15
2.4.3 11 / 15
2.3.4 11 / 15
2.3.3 11 / 15
2.3.2 11 / 15
2.3.1 11 / 15

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.1

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.5

1 finding
LOW No provenance attestation provenance

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

v2.4.4

1 finding
LOW No provenance attestation provenance

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

v2.4.3

1 finding
LOW No provenance attestation provenance

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

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.