@platforma-open/milaboratories.clonotype-enrichment No license 28 versions

@platforma-open/milaboratories.clonotype-enrichment

npm

28

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
provenance	publisher-changed	AI (provenance): mike-ainsel is an established publisher in the same org with 37 approved packages; transition appears legitimate.	ai	2026/05/08
bogus-package	bogus-package	AI (bogus-package): Intentional thin manifest/aggregator package; tiny payload and missing npm metadata are expected for this pattern.	ai	2026/05/05
phantom-deps	phantom-dep:@platforma-open/milaboratories.clonotype-enrichment.ui	AI (phantom-deps): Same-org sub-component referenced via block config, not direct import; stable false positive for this package type.	ai	2026/05/05
phantom-deps	phantom-dep:@platforma-open/milaboratories.clonotype-enrichment.model	AI (phantom-deps): Same-org sub-component referenced via block config, not direct import; stable false positive for this package type.	ai	2026/05/05
phantom-deps	phantom-dep:@platforma-open/milaboratories.clonotype-enrichment.workflow	AI (phantom-deps): Same-org sub-component referenced via block config, not direct import; stable false positive for this package type.	ai	2026/05/05

Versions (showing 28 of 28)

Version	Deps	Published
3.0.5	3 / 1	2026-05-19
3.0.4	3 / 1	2026-05-08
3.0.3	3 / 1	2026-05-07
3.0.2	3 / 1	2026-05-06
3.0.1	3 / 1	2026-04-30
3.0.0	3 / 1	2026-04-30
2.2.46	3 / 1	2026-04-22
2.2.45	3 / 1	2026-04-10
2.2.44	3 / 1	2026-04-10
2.2.43	3 / 1	2026-03-26
2.2.42	3 / 1	2026-03-25
2.2.41	3 / 1	2026-03-24
2.2.40	3 / 1	2026-02-26
2.2.39	3 / 1	2026-02-20
2.2.38	3 / 1	2026-02-18
2.2.37	3 / 1	2026-02-13
2.2.36	3 / 1	2026-02-13
2.2.35	3 / 1	2026-02-13
2.2.34	3 / 1	2026-02-06
2.2.33	3 / 1	2026-02-03
2.2.32	3 / 1	2026-01-30
2.2.31	3 / 1	2026-01-27
2.2.30	3 / 1	2026-01-20
2.2.29	3 / 1	2026-01-14
2.2.28	3 / 1	2026-01-13
2.2.27	3 / 1	2026-01-08
2.2.26	3 / 1	2026-01-02
2.2.25	3 / 1	2025-11-14

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.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.

v3.0.0

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-04-30) provenance

This version was published by a different npm account than previous versions on 2026-04-30. 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.

v2.2.46

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-04-22) provenance

This version was published by a different npm account than previous versions on 2026-04-22. 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.

v2.2.45

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-04-10) provenance

This version was published by a different npm account than previous versions on 2026-04-10. 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.

v2.2.44

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-04-10) provenance

This version was published by a different npm account than previous versions on 2026-04-10. 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.

v2.2.43

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-03-26) provenance

This version was published by a different npm account than previous versions on 2026-03-26. 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.

v2.2.42

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-03-25) provenance

This version was published by a different npm account than previous versions on 2026-03-25. 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.

v2.2.41

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-03-24) provenance

This version was published by a different npm account than previous versions on 2026-03-24. 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.

v2.2.40

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-26) provenance

This version was published by a different npm account than previous versions on 2026-02-26. 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.

v2.2.39

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-20) provenance

This version was published by a different npm account than previous versions on 2026-02-20. 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.

v2.2.38

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. 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.

v2.2.37

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-13) provenance

This version was published by a different npm account than previous versions on 2026-02-13. 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.

v2.2.36

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-13) provenance

This version was published by a different npm account than previous versions on 2026-02-13. 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.

v2.2.35

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-13) provenance

This version was published by a different npm account than previous versions on 2026-02-13. 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.

v2.2.34

2 findings

HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-06) provenance

This version was published by a different npm account than previous versions on 2026-02-06. 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.

v2.2.33

1 finding

LOW No provenance attestation provenance

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

v2.2.32

1 finding

LOW No provenance attestation provenance

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

v2.2.31

1 finding

LOW No provenance attestation provenance

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

v2.2.30

1 finding

LOW No provenance attestation provenance

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

v2.2.29

1 finding

LOW No provenance attestation provenance

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

v2.2.28

1 finding

LOW No provenance attestation provenance

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

v2.2.27

1 finding

LOW No provenance attestation provenance

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

v2.2.26

1 finding

LOW No provenance attestation provenance

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

v2.2.25

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.