babel-plugin-import — Greenflagged

Component modular import plugin for babel.

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

sorryccafc163paranoidjkpeachscriptzombiej

Keywords

babel-pluginantd

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is intentional: loads user-supplied customName module as documented plugin API.	ai	2026/05/26
maintainer-change	maintainer-removed	AI (maintainer-change): yesmeck removal is a routine maintainer cleanup; sorrycc is the original author and active publisher.	ai	2026/05/26
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is a historical stub for this well-established package (444k weekly downloads, 40 versions, trusted publisher afc163). Not indicative of malice.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Stub version 0.0.0 of a legitimate, widely-used package. Sparse metadata is expected for this historical placeholder, not a spam/malware indicator.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within ant-design org; zombiej is a known long-standing contributor.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): peachscript and zombiej are known ant-design team members; legitimate org handoff.	ai	2026/04/24

Versions (showing 38 of 38)

Version	Deps	Published
1.13.8	1 / 18	2023-07-26
1.13.7	1 / 18	2023-07-26
1.13.6	1 / 18	2023-01-05
1.13.5	1 / 18	2022-04-14
1.13.4	2 / 18	2022-04-11
1.13.3	2 / 18	2020-11-24
1.13.2	2 / 17	2020-11-24
1.13.1	2 / 17	2020-10-10
1.13.0	2 / 12	2019-11-25
1.12.2	2 / 12	2019-09-23
1.12.1	2 / 12	2019-08-28
1.12.0	2 / 11	2019-06-01
1.11.2	2 / 11	2019-05-17
1.11.0	2 / 11	2018-10-29
1.10.0	2 / 14	2018-10-17
1.9.1	2 / 14	2018-09-16
1.9.0	1 / 15	2018-09-16
1.8.0	1 / 16	2018-06-12
1.7.0	1 / 16	2018-04-04
1.6.7	1 / 16	2018-03-15
1.6.6	1 / 16	2018-03-08
1.6.5	1 / 16	2018-02-17
1.6.4	1 / 16	2018-02-13
1.6.3	1 / 14	2017-12-11
1.6.2	1 / 17	2017-10-16
1.6.1	0 / 16	2017-10-12
1.6.0	0 / 16	2017-09-28
1.5.0	0 / 15	2017-09-20
1.4.0	0 / 15	2017-08-14
1.3.1	0 / 15	2017-07-31
1.3.0	0 / 15	2017-07-31
1.2.1	0 / 15	2017-05-31
1.2.0	0 / 15	2017-05-25
1.1.1	0 / 15	2017-02-17
1.1.0	0 / 15	2016-11-18
1.0.1	0 / 14	2016-09-28
1.0.0	0 / 14	2016-09-20
0.0.0	0 / 0	2016-09-14

v1.13.8

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: zombiej → sorrycc (on 2023-07-26, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (zombiej) on 2023-07-26, but sorrycc 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.

v1.13.7

2 findings

HIGH Publisher changed: sorrycc → zombiej (on 2023-07-26) provenance

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

v1.13.6

1 finding

LOW No provenance attestation provenance

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

v1.13.5

1 finding

LOW No provenance attestation provenance

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

v1.13.4

1 finding

LOW No provenance attestation provenance

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

v1.13.3

1 finding

LOW No provenance attestation provenance

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

v1.13.2

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.2

1 finding

LOW No provenance attestation provenance

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

v1.12.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: yesmeck → sorrycc (on 2019-08-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-28. This could indicate a legitimate maintainer transition or an account compromise.

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.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: sorrycc → yesmeck (on 2019-05-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-17. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.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: yesmeck → sorrycc (on 2018-09-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-16. This could indicate a legitimate maintainer transition or an account compromise.

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

2 findings

HIGH Publisher changed: sorrycc → yesmeck (on 2018-04-04) provenance

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

v1.6.7

2 findings

HIGH Publisher changed: yesmeck → sorrycc (on 2018-03-15) provenance

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

v1.6.6

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.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: sorrycc → yesmeck (on 2018-02-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-13. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.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: afc163 → sorrycc (on 2017-05-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-25. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.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: afc163 → sorrycc (on 2016-09-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-28. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.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: afc163 → sorrycc (on 2016-09-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-20. This could indicate a legitimate maintainer transition or an account compromise.

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