source-map-support — Greenflagged

Fixes stack traces for files with source maps

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

linusuevanwjulien-f

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	source-size-tripled	AI (source-diff): Size increase is entirely from the added webpack test bundle (~477KB); expected for adding webpack test support.	ai	2026/04/24
source-diff	net-exec-file:webpack-test/compiled.js	AI (source-diff): Webpack test bundle naturally contains bundled source-map-support code; network+exec pattern is false positive.	ai	2026/04/24
source-diff	obfuscated-file:webpack-test/compiled.js	AI (source-diff): webpack-test/compiled.js is a standard webpack bundle output for tests, not obfuscated malicious code.	ai	2026/04/24
source-diff	net-exec-file:amd-test/require.js	AI (source-diff): File is RequireJS 2.1.9 (Dojo Foundation AMD loader) used as a test fixture. Network+exec pattern is inherent to AMD loaders, not malware.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition to linusu in 2015; linusu is a well-established publisher with extensive track record.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() is in a bundled copy of RequireJS inside amd-test/ (test infrastructure), not in runtime code. Stable false positive for this package.	ai	2026/04/23
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): The raw IP 127.0.0.1 is localhost, used in a test server (header-test/server.js). Not an exfiltration or C2 endpoint.	ai	2026/04/23
semgrep	semgrep:child-process-exec	AI (semgrep): child_process.exec is in build.js only, a developer build script not executed at install or runtime. Stable false positive.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): child_process is used only in build.js (a build script), not in runtime or install scripts. No execution at install time.	ai	2026/04/23

Versions (showing 66 of 66)

Version	Deps	Published
0.5.21	2 / 5	2021-11-19
0.5.20	2 / 5	2021-09-09
0.5.19	2 / 5	2020-04-24
0.5.18	2 / 5	2020-04-21
0.5.17	2 / 5	2020-04-19
0.5.16	2 / 5	2019-10-29
0.5.15	2 / 5	2019-10-28
0.5.14	2 / 5	2019-10-28
0.5.13	2 / 5	2019-07-31
0.5.12	2 / 5	2019-04-08
0.5.11	2 / 5	2019-03-12
0.5.10	2 / 5	2019-01-11
0.5.9	2 / 5	2018-08-20
0.5.8	2 / 5	2018-08-09
0.5.7	2 / 5	2018-08-09
0.5.6	2 / 5	2018-05-13
0.5.5	2 / 5	2018-04-25
0.5.4	1 / 5	2018-03-15
0.5.3	1 / 5	2018-01-25
0.5.2	1 / 5	2018-01-19
0.5.1	1 / 5	2018-01-16
0.5.0	1 / 5	2017-10-03
0.4.18	1 / 5	2017-09-10
0.4.17	1 / 5	2017-09-02
0.4.16	1 / 5	2017-08-17
0.4.15	1 / 5	2017-04-28
0.4.14	1 / 5	2017-03-18
0.4.13	1 / 5	2017-03-16
0.4.12	1 / 5	2017-03-13
0.4.11	1 / 5	2017-01-27
0.4.10	1 / 5	2017-01-17
0.4.9	1 / 5	2017-01-15
0.4.8	1 / 4	2016-12-25
0.4.7	1 / 4	2016-12-22
0.4.6	1 / 4	2016-10-30
0.4.5	1 / 4	2016-10-18
0.4.4	1 / 4	2016-10-16
0.4.3	1 / 4	2016-09-29
0.4.2	1 / 4	2016-07-14
0.4.1	1 / 4	2016-06-29
0.4.0	1 / 4	2015-11-30
0.3.3	1 / 4	2015-10-23
0.3.2	1 / 3	2015-06-25
0.3.1	1 / 3	2015-05-30
0.3.0	1 / 3	2015-05-29
0.2.10	1 / 3	2015-03-12
0.2.9	1 / 3	2015-01-08
0.2.8	1 / 3	2014-10-22
0.2.7	1 / 3	2014-07-03
0.2.6	1 / 3	2014-04-26
0.2.5	1 / 3	2013-11-14
0.2.4	1 / 1	2013-11-10
0.2.3	1 / 1	2013-09-05
0.2.2	1 / 1	2013-08-16
0.2.1	1 / 1	2013-08-03
0.2.0	1 / 1	2013-07-21
0.1.9	1 / 1	2013-07-21
0.1.8	1 / 1	2013-06-27
0.1.7	1 / 1	2013-06-27
0.1.6	1 / 1	2013-06-11
0.1.5	1 / 1	2013-05-04
0.1.4	1 / 1	2013-04-28
0.1.3	1 / 1	2013-04-25
0.1.2	1 / 1	2013-03-10
0.1.1	1 / 1	2013-03-05
0.1.0	1 / 1	2013-01-18

v0.5.20

1 finding

LOW No provenance attestation provenance

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

v0.5.19

1 finding

LOW No provenance attestation provenance

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

v0.5.18

1 finding

LOW No provenance attestation provenance

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

v0.5.17

1 finding

LOW No provenance attestation provenance

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

v0.5.16

1 finding

LOW No provenance attestation provenance

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

v0.5.15

1 finding

LOW No provenance attestation provenance

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

v0.5.14

1 finding

LOW No provenance attestation provenance

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

v0.5.12

1 finding

LOW No provenance attestation provenance

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

v0.5.11

1 finding

LOW No provenance attestation provenance

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

v0.5.10

1 finding

LOW No provenance attestation provenance

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

v0.5.9

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

1 finding

LOW No provenance attestation provenance

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

v0.4.14

1 finding

LOW No provenance attestation provenance

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

v0.4.13

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.11

1 finding

LOW No provenance attestation provenance

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

v0.4.10

3 findings

HIGH New obfuscated file: webpack-test/compiled.js 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: webpack-test/compiled.js 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.

v0.4.9

3 findings

HIGH New obfuscated file: webpack-test/compiled.js 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: webpack-test/compiled.js 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.

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

2 findings

HIGH Publisher changed: julien-f → linusu (on 2015-11-30) provenance

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

v0.3.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: evanw → julien-f (on 2015-10-23) provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

2 findings

HIGH New file with network + code execution: amd-test/require.js 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.

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

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

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

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

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

v0.1.9

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.

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

v0.1.7

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.

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

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

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

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

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

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

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