← Home

@datagrok/hit-triage

npm Repository Homepage

Hit Triage helps chemists assess the quality of hits and decide which compounds should make it to the next stage.

11
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

aparamonov_datagrokskalkindrizhinappolovyi_datagrokaleksashka_11

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ts-loader AI (phantom-deps): Webpack build tool; referenced in webpack config, not a runtime import. ai
phantom-deps phantom-dep:css-loader AI (phantom-deps): Webpack build tool; referenced in webpack config, not a runtime import. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): Build-time compiler; referenced in tsconfig/webpack, not a runtime import. ai
phantom-deps phantom-dep:style-loader AI (phantom-deps): Webpack build tool; referenced in webpack config, not a runtime import. ai
phantom-deps phantom-dep:source-map-loader AI (phantom-deps): Webpack build tool; referenced in webpack config, not a runtime import. ai
phantom-deps phantom-dep:uuid AI (phantom-deps): Utility used via config/indirect reference; stable false positive for this package. ai
phantom-deps phantom-dep:typeahead-standalone AI (phantom-deps): UI dependency referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@datagrok-libraries/compute-utils AI (phantom-deps): Sibling Datagrok library; referenced in config, stable false positive. ai

Versions (showing 11 of 11)

Version Deps Published
1.10.2 15 / 8
1.10.1 15 / 8
1.10.0 15 / 8
1.9.2 13 / 8
1.9.1 13 / 8
1.9.0 12 / 8
1.8.0 12 / 8
1.7.7 12 / 8
1.7.6 12 / 8
1.7.5 12 / 8
1.7.4 12 / 8

v1.10.2

1 finding
LOW No provenance attestation provenance

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

v1.10.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.

v1.10.0

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.

v1.9.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.

v1.9.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.

v1.9.0

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.

v1.8.0

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.

v1.7.7

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.

v1.7.6

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.

v1.7.5

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.

v1.7.4

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.