systemjs — Greenflagged

Dynamic ES module loader

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

joeldenningguybedford

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/system-node.cjs	AI (source-diff): dist/system-node.cjs is a legitimate webpack/ncc bundle of the SystemJS Node.js build. The 'obfuscation' is standard webpack boilerplate, not malicious code.	ai	2026/04/24
source-diff	net-exec-file:dist/system-node.cjs	AI (source-diff): SystemJS is a dynamic module loader by design — network fetching and dynamic code execution are its core functionality, not malware indicators.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is explained by the addition of a ncc-bundled Node.js distribution artifact (system-node.cjs), a legitimate architectural change.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): guybedford is the original author of systemjs; the transition from joeldenning back to guybedford is a legitimate maintainer change, not a compromise.	ai	2026/04/24

Versions (showing 100 of 226)

Version	Deps	Published
6.15.1	0 / 19	2024-04-27
6.15.0	0 / 19	2024-04-27
6.14.3	0 / 19	2024-01-01
6.14.2	0 / 19	2023-08-16
6.14.1	0 / 19	2023-03-21
6.14.0	0 / 19	2023-02-25
6.13.0	0 / 19	2022-09-29
6.12.6	0 / 19	2022-08-31
6.12.5	0 / 19	2022-08-31
6.12.4	0 / 19	2022-08-26
6.12.3	0 / 19	2022-08-18
6.12.2	0 / 19	2022-08-10
6.12.1	0 / 20	2022-01-21
6.12.0	0 / 20	2022-01-21
6.11.0	0 / 20	2021-10-18
6.10.3	0 / 20	2021-08-17
6.10.2	0 / 20	2021-07-04
6.10.1	0 / 20	2021-06-14
6.10.0	0 / 20	2021-06-07
6.9.0	0 / 20	2021-05-12
6.8.3	0 / 20	2020-12-31
6.8.2	0 / 20	2020-12-16
6.8.1	0 / 20	2020-11-30
6.8.0	0 / 20	2020-11-26
6.7.1	0 / 20	2020-10-12
6.7.0	0 / 20	2020-10-09
6.6.1	0 / 20	2020-09-12
6.6.0	0 / 20	2020-09-12
6.5.1	0 / 20	2020-09-02
6.5.0	0 / 20	2020-08-10
6.4.3	0 / 20	2020-08-06
6.4.2	0 / 20	2020-08-05
6.4.1	0 / 20	2020-07-31
6.4.0	0 / 20	2020-07-23
6.3.3	0 / 20	2020-06-27
6.3.2	0 / 20	2020-05-18
6.3.1	0 / 20	2020-04-14
6.3.0	0 / 19	2020-04-09
6.2.6	0 / 9	2020-03-15
6.2.5	0 / 9	2020-02-27
6.2.4	0 / 9	2020-02-24
6.2.3	0 / 9	2020-02-14
6.2.2	0 / 9	2020-02-07
6.2.1	0 / 9	2020-02-06
6.2.0	0 / 9	2020-02-01
6.1.10	0 / 9	2020-01-28
6.1.9	0 / 9	2020-01-11
6.1.8	0 / 9	2020-01-10
6.1.7	0 / 9	2019-11-29
6.1.6	0 / 9	2019-11-29
6.1.5	0 / 9	2019-11-22
6.1.4	0 / 9	2019-10-13
6.1.3	0 / 9	2019-10-06
6.1.2	0 / 9	2019-09-22
6.1.1	0 / 9	2019-09-13
6.1.0	0 / 9	2019-09-11
6.0.0	0 / 9	2019-08-29
5.0.0	0 / 7	2019-07-31
4.1.1	0 / 7	2019-07-31
4.1.0	0 / 7	2019-07-14
4.0.2	0 / 7	2019-07-08
4.0.1	0 / 7	2019-07-06
4.0.0	0 / 7	2019-06-30
3.1.6	0 / 7	2019-04-21
3.1.5	0 / 7	2019-04-19
3.1.4	0 / 7	2019-04-19
3.1.3	0 / 7	2019-04-18
3.1.2	0 / 7	2019-04-13
3.1.1	0 / 7	2019-04-07
3.1.0	0 / 7	2019-03-24
3.0.2	0 / 11	2019-03-17
3.0.1	0 / 11	2019-03-03
3.0.0	0 / 11	2019-01-12
2.1.2	0 / 11	2019-01-11
2.1.1	0 / 11	2018-11-01
2.1.0	0 / 11	2018-11-01
2.0.2	0 / 11	2018-10-06
2.0.1	0 / 11	2018-10-02
2.0.0	0 / 11	2018-09-28
0.21.6	0 / 14	2019-01-15
0.21.5	0 / 14	2018-09-23
0.21.4	0 / 14	2018-05-31
0.21.3	0 / 14	2018-04-16
0.21.2	0 / 14	2018-04-04
0.21.1	0 / 14	2018-03-30
0.21.0	0 / 14	2018-02-06
0.20.19	0 / 16	2017-09-18
0.20.18	0 / 16	2017-08-20
0.20.17	0 / 16	2017-07-26
0.20.16	0 / 16	2017-07-23
0.20.15	0 / 15	2017-07-10
0.20.14	0 / 15	2017-06-14
0.20.13	0 / 15	2017-05-30
0.20.12	0 / 15	2017-04-06
0.20.11	0 / 15	2017-03-30
0.20.10	0 / 15	2017-03-16
0.20.9	0 / 15	2017-02-17
0.20.8	0 / 15	2017-02-16
0.20.7	0 / 15	2017-02-09
0.20.6	0 / 15	2017-02-09

Showing 100 of 226 Next page →

v6.15.1

1 finding

LOW No provenance attestation provenance

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

v6.15.0

1 finding

LOW No provenance attestation provenance

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

v6.14.3

1 finding

LOW No provenance attestation provenance

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

v6.14.2

1 finding

LOW No provenance attestation provenance

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

v6.14.1

1 finding

LOW No provenance attestation provenance

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

v6.14.0

1 finding

LOW No provenance attestation provenance

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

v6.13.0

1 finding

LOW No provenance attestation provenance

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

v6.12.6

1 finding

LOW No provenance attestation provenance

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

v6.12.5

1 finding

LOW No provenance attestation provenance

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

v6.12.4

1 finding

LOW No provenance attestation provenance

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

v6.12.3

1 finding

LOW No provenance attestation provenance

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

v6.12.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: joeldenning → guybedford (on 2022-08-10) provenance

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

v6.12.1

1 finding

LOW No provenance attestation provenance

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

v6.12.0

1 finding

LOW No provenance attestation provenance

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

v6.11.0

1 finding

LOW No provenance attestation provenance

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

v6.10.3

1 finding

LOW No provenance attestation provenance

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

v6.10.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: guybedford → joeldenning (on 2021-07-04) provenance

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

v6.10.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: joeldenning → guybedford (on 2021-06-14) provenance

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

v6.10.0

1 finding

LOW No provenance attestation provenance

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

v6.9.0

1 finding

LOW No provenance attestation provenance

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

v6.8.3

1 finding

LOW No provenance attestation provenance

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

v6.8.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: guybedford → joeldenning (on 2020-12-16) provenance

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

v6.8.1

1 finding

LOW No provenance attestation provenance

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

v6.8.0

1 finding

LOW No provenance attestation provenance

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

v6.7.1

1 finding

LOW No provenance attestation provenance

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

v6.7.0

1 finding

LOW No provenance attestation provenance

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

v6.6.1

1 finding

LOW No provenance attestation provenance

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

v6.6.0

1 finding

LOW No provenance attestation provenance

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

v6.5.1

1 finding

LOW No provenance attestation provenance

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

v6.5.0

1 finding

LOW No provenance attestation provenance

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

v6.4.3

1 finding

LOW No provenance attestation provenance

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

v6.4.2

1 finding

LOW No provenance attestation provenance

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

v6.4.1

1 finding

LOW No provenance attestation provenance

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

v6.4.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: joeldenning → guybedford (on 2020-07-23) provenance

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

v6.3.3

1 finding

LOW No provenance attestation provenance

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

v6.3.2

1 finding

LOW No provenance attestation provenance

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

v6.3.1

2 findings

HIGH New file with network + code execution: dist/system-node.cjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v6.3.0

3 findings

HIGH New obfuscated file: dist/system-node.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/system-node.cjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v6.2.6

1 finding

LOW No provenance attestation provenance

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

v6.2.5

1 finding

LOW No provenance attestation provenance

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

v6.2.4

1 finding

LOW No provenance attestation provenance

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

v6.2.3

1 finding

LOW No provenance attestation provenance

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

v6.2.2

1 finding

LOW No provenance attestation provenance

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

v6.2.1

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.10

1 finding

LOW No provenance attestation provenance

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

v6.1.9

1 finding

LOW No provenance attestation provenance

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

v6.1.8

1 finding

LOW No provenance attestation provenance

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

v6.1.7

1 finding

LOW No provenance attestation provenance

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

v6.1.6

1 finding

LOW No provenance attestation provenance

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

v6.1.5

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: guybedford → joeldenning (on 2019-11-22) provenance

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

v6.1.4

1 finding

LOW No provenance attestation provenance

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

v6.1.3

2 findings

HIGH Publisher changed: joeldenning → guybedford (on 2019-10-06) provenance

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

v6.1.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.

v6.1.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.

v6.1.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.

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

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