@datagrok-libraries/bio No license 41 versions

@datagrok-libraries/bio

npm

Bio utilities, types supporting Macromolecule, Molecule3D data

41

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_datagrokspodgrok

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Established scoped org package with 320 versions; sparse metadata is a consistent pattern, not spam.	ai	2026/05/13
typosquat	typosquat.levenshtein:pino	AI (typosquat): Scoped @datagrok-libraries package; Levenshtein match to 'pino' is a clear false positive.	ai	2026/05/02
phantom-deps	phantom-dep:uuid	AI (phantom-deps): uuid is a declared runtime dep in a large library; config-only reference is a heuristic FP.	ai	2026/05/02
phantom-deps	phantom-dep:dayjs	AI (phantom-deps): dayjs is a declared runtime dep; phantom-dep heuristic FP for this package.	ai	2026/05/02
phantom-deps	phantom-dep:cash-dom	AI (phantom-deps): cash-dom is a declared runtime dep; phantom-dep heuristic FP for this package.	ai	2026/05/02
phantom-deps	phantom-dep:fastest-levenshtein	AI (phantom-deps): fastest-levenshtein is a declared runtime dep; phantom-dep heuristic FP for this package.	ai	2026/05/02

Versions (showing 41 of 41)

Version	Deps	Published
5.65.2	15 / 14	2026-05-16
5.65.1	15 / 14	2026-05-07
5.65.0	15 / 14	2026-05-01
5.64.1	15 / 14	2026-05-01
5.64.0	15 / 14	2026-04-29
5.63.7	15 / 14	2026-04-15
5.63.6	15 / 14	2026-04-03
5.63.5	15 / 14	2026-03-30
5.63.4	15 / 14	2026-03-29
5.63.3	15 / 14	2026-03-10
5.63.2	15 / 14	2026-03-06
5.63.1	15 / 14	2026-03-06
5.63.0	15 / 14	2026-03-04
5.62.1	15 / 13	2026-03-01
5.62.0	15 / 13	2026-02-26
5.61.6	15 / 13	2026-02-20
5.61.5	15 / 13	2026-02-20
5.61.4	15 / 14	2025-11-28
5.61.3	15 / 14	2025-11-04
5.61.2	15 / 14	2025-11-03
5.61.0	15 / 14	2025-10-29
5.60.0	15 / 14	2025-10-28
5.55.0	15 / 14	2025-10-03
5.54.9	15 / 14	2025-09-16
5.54.8	15 / 14	2025-08-28
5.54.7	15 / 14	2025-08-18
5.54.6	15 / 14	2025-08-06
5.54.5	15 / 14	2025-08-03
5.54.4	15 / 14	2025-08-01
5.54.3	15 / 14	2025-07-31
5.54.2	15 / 14	2025-07-03
5.54.1	15 / 14	2025-06-25
5.54.0	15 / 14	2025-06-18
5.53.4	15 / 14	2025-06-03
5.53.3	15 / 14	2025-06-02
5.53.2	15 / 14	2025-05-29
5.53.1	15 / 14	2025-05-15
5.53.0	15 / 14	2025-05-15
5.52.2	15 / 14	2025-05-14
5.52.1	15 / 14	2025-05-13
5.52.0	15 / 14	2025-05-12

v5.65.2

1 finding

LOW No provenance attestation provenance

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

v5.65.1

1 finding

LOW No provenance attestation provenance

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

v5.65.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.

v5.64.1

1 finding

LOW No provenance attestation provenance

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

v5.64.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.

v5.63.7

1 finding

LOW No provenance attestation provenance

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

v5.63.6

1 finding

LOW No provenance attestation provenance

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

v5.63.5

1 finding

LOW No provenance attestation provenance

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

v5.63.4

1 finding

LOW No provenance attestation provenance

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

v5.63.3

1 finding

LOW No provenance attestation provenance

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

v5.63.2

1 finding

LOW No provenance attestation provenance

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

v5.63.1

1 finding

LOW No provenance attestation provenance

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

v5.63.0

1 finding

LOW No provenance attestation provenance

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

v5.62.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.

v5.62.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.

v5.61.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.

v5.61.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.

v5.61.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.

v5.61.3

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.

v5.61.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.

v5.61.0

2 findings

HIGH Publisher changed: spodgrok → aparamonov_datagrok (on 2025-10-29) provenance

This version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.60.0

2 findings

HIGH Publisher changed: spodgrok → aparamonov_datagrok (on 2025-10-28) provenance

This version was published by a different npm account than previous versions on 2025-10-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.55.0

2 findings

HIGH Publisher changed: spodgrok → aparamonov_datagrok (on 2025-10-03) provenance

This version was published by a different npm account than previous versions on 2025-10-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.54.9

1 finding

LOW No provenance attestation provenance

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

v5.54.8

1 finding

LOW No provenance attestation provenance

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

v5.54.7

1 finding

LOW No provenance attestation provenance

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

v5.54.6

1 finding

LOW No provenance attestation provenance

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

v5.54.5

1 finding

LOW No provenance attestation provenance

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

v5.54.4

1 finding

LOW No provenance attestation provenance

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

v5.54.3

1 finding

LOW No provenance attestation provenance

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

v5.54.2

1 finding

LOW No provenance attestation provenance

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

v5.54.1

1 finding

LOW No provenance attestation provenance

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

v5.54.0

1 finding

LOW No provenance attestation provenance

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

v5.53.4

1 finding

LOW No provenance attestation provenance

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

v5.53.3

1 finding

LOW No provenance attestation provenance

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

v5.53.2

1 finding

LOW No provenance attestation provenance

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

v5.53.1

1 finding

LOW No provenance attestation provenance

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

v5.53.0

1 finding

LOW No provenance attestation provenance

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

v5.52.2

1 finding

LOW No provenance attestation provenance

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

v5.52.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.

v5.52.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.