@platforma-open/milaboratories.mixcr-clonotyping-2 No license 51 versions

@platforma-open/milaboratories.mixcr-clonotyping-2

npm

51

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mike-ainseldbolotin_mi

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): Intentional thin aggregator/bundle package in a monorepo; tiny payload and no keywords are expected for this pattern.	ai	2026/05/22
phantom-deps	phantom-dep:@platforma-sdk/model	AI (phantom-deps): Used in block config metadata, not direct JS imports; stable false positive for this package type.	ai	2026/05/22
phantom-deps	phantom-dep:@platforma-open/milaboratories.mixcr-clonotyping-2.ui	AI (phantom-deps): Referenced via block config path, not direct JS import; expected pattern for this aggregator.	ai	2026/05/22
phantom-deps	phantom-dep:@platforma-open/milaboratories.mixcr-clonotyping-2.model	AI (phantom-deps): Referenced via block config path, not direct JS import; expected pattern for this aggregator.	ai	2026/05/22
phantom-deps	phantom-dep:@platforma-open/milaboratories.mixcr-clonotyping-2.workflow	AI (phantom-deps): Referenced via block config path, not direct JS import; expected pattern for this aggregator.	ai	2026/05/22

Versions (showing 51 of 109)

View all versions

Version	Deps	Published
2.18.5	4 / 1	2026-05-21
2.18.4	4 / 1	2026-05-08
2.18.3	4 / 1	2026-04-28
2.18.2	4 / 1	2026-04-16
2.18.1	4 / 1	2026-04-15
2.18.0	4 / 1	2026-04-09
2.17.8	4 / 1	2026-04-03
2.17.7	4 / 1	2026-03-27
2.17.6	4 / 1	2026-03-26
2.17.5	4 / 1	2026-03-23
2.17.4	4 / 1	2026-03-17
2.17.3	4 / 1	2026-03-16
2.17.2	4 / 1	2026-03-11
2.17.1	4 / 1	2026-03-03
2.17.0	4 / 1	2026-03-02
2.16.6	4 / 1	2026-02-24
2.16.5	4 / 1	2026-02-16
2.16.4	4 / 1	2026-02-13
2.16.3	4 / 1	2026-02-13
2.16.2	4 / 1	2026-02-12
2.16.1	4 / 1	2026-02-11
2.16.0	4 / 1	2026-02-10
2.15.2	4 / 1	2026-01-21
2.15.1	4 / 1	2026-01-20
2.15.0	4 / 1	2026-01-20
2.14.0	4 / 1	2026-01-19
2.13.0	4 / 1	2026-01-16
2.12.27	4 / 1	2025-12-15
2.12.26	4 / 1	2025-12-09
2.12.25	4 / 1	2025-12-09
2.12.24	4 / 1	2025-12-09
2.12.23	4 / 1	2025-12-01
2.12.22	4 / 1	2025-11-09
2.12.21	4 / 1	2025-11-06
2.12.20	4 / 1	2025-11-05
2.12.19	4 / 1	2025-11-03
2.12.18	4 / 1	2025-10-30
2.12.17	4 / 1	2025-10-28
2.12.16	4 / 1	2025-10-26
2.12.15	4 / 1	2025-10-26
2.12.14	4 / 1	2025-10-23
2.12.13	4 / 1	2025-10-22
2.12.12	4 / 1	2025-10-21
2.12.11	4 / 1	2025-10-21
2.12.10	4 / 1	2025-10-14
2.12.9	4 / 1	2025-10-14
2.12.8	4 / 1	2025-10-13
2.12.7	4 / 1	2025-10-07
2.12.6	4 / 1	2025-10-02
2.12.5	4 / 1	2025-09-24
2.12.4	4 / 1	2025-09-24

v2.18.5

1 finding

LOW No provenance attestation provenance

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

v2.18.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.

v2.18.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.

v2.18.2

1 finding

LOW No provenance attestation provenance

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

v2.18.1

1 finding

LOW No provenance attestation provenance

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

v2.18.0

1 finding

LOW No provenance attestation provenance

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

v2.17.8

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.17.7

1 finding

LOW No provenance attestation provenance

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

v2.17.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.

v2.17.5

1 finding

LOW No provenance attestation provenance

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

v2.17.4

1 finding

LOW No provenance attestation provenance

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

v2.17.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.

v2.17.2

1 finding

LOW No provenance attestation provenance

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

v2.17.1

1 finding

LOW No provenance attestation provenance

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

v2.17.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.

v2.16.6

1 finding

LOW No provenance attestation provenance

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

v2.16.5

1 finding

LOW No provenance attestation provenance

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

v2.16.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-13, known maintainer) provenance

This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-13, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.16.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-13, known maintainer) provenance

This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-13, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.16.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-12, known maintainer) provenance

This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-12, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.16.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-11, known maintainer) provenance

This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-11, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.16.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-10, known maintainer) provenance

This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-10, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.15.2

1 finding

LOW No provenance attestation provenance

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

v2.15.1

1 finding

LOW No provenance attestation provenance

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

v2.15.0

1 finding

LOW No provenance attestation provenance

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

v2.14.0

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.27

1 finding

LOW No provenance attestation provenance

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

v2.12.26

1 finding

LOW No provenance attestation provenance

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

v2.12.25

1 finding

LOW No provenance attestation provenance

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

v2.12.24

1 finding

LOW No provenance attestation provenance

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

v2.12.23

1 finding

LOW No provenance attestation provenance

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

v2.12.22

1 finding

LOW No provenance attestation provenance

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

v2.12.21

1 finding

LOW No provenance attestation provenance

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

v2.12.20

1 finding

LOW No provenance attestation provenance

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

v2.12.19

1 finding

LOW No provenance attestation provenance

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

v2.12.18

1 finding

LOW No provenance attestation provenance

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

v2.12.17

1 finding

LOW No provenance attestation provenance

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

v2.12.16

1 finding

LOW No provenance attestation provenance

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

v2.12.15

1 finding

LOW No provenance attestation provenance

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

v2.12.14

1 finding

LOW No provenance attestation provenance

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

v2.12.13

1 finding

LOW No provenance attestation provenance

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

v2.12.12

1 finding

LOW No provenance attestation provenance

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

v2.12.11

1 finding

LOW No provenance attestation provenance

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

v2.12.10

1 finding

LOW No provenance attestation provenance

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

v2.12.9

1 finding

LOW No provenance attestation provenance

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

v2.12.8

1 finding

LOW No provenance attestation provenance

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

v2.12.7

1 finding

LOW No provenance attestation provenance

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

v2.12.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.

v2.12.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.

v2.12.4

1 finding

LOW No provenance attestation provenance

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