nise BSD-3-Clause 63 versions

nise

npm Repository Homepage

Fake XHR and server

63

Versions

BSD-3-Clause

License

No

Install Scripts

Missing

Provenance

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

fatso83cjohansenmantonimrgnrdrck

Keywords

testtestingfakemockxhrserver

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): fatso83 is a long-standing sinonjs maintainer (451 approved packages, 3786 days history). The 2021 transition is a legitimate org handoff, not a compromise.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() is used to execute timer function strings, replicating browser setTimeout(string) behavior. This is standard and expected in fake-timer implementations.	ai	2026/04/24
dependencies	unvetted-dep:@sinonjs/text-encoding	AI (dependencies): @sinonjs/text-encoding is a first-party sinonjs package, consistent with nise's sinonjs ecosystem dependencies. Legitimate and expected for fake XHR functionality.	ai	2026/04/23

Versions (showing 63 of 63)

Version	Deps	Published
6.1.5	4 / 16	2026-04-11
6.1.4	4 / 15	2026-03-16
6.1.3	4 / 15	2026-03-03
6.1.2	5 / 15	2026-03-02
6.1.1	5 / 15	2024-09-13
6.1.0	5 / 15	2024-09-12
6.0.1	5 / 15	2024-09-10
6.0.0	5 / 15	2024-05-15
5.1.9	5 / 15	2024-01-31
5.1.8	5 / 15	2024-01-31
5.1.7	5 / 15	2024-01-09
5.1.6	6 / 14	2024-01-09
5.1.5	5 / 15	2023-10-20
5.1.4	5 / 15	2022-12-19
5.1.3	5 / 15	2022-12-05
5.1.2	5 / 15	2022-11-07
5.1.1	5 / 15	2022-02-01
5.1.0	5 / 15	2021-05-25
5.0.4	5 / 15	2021-05-20
5.0.3	5 / 15	2021-05-14
5.0.2	5 / 15	2021-04-11
5.0.1	5 / 15	2021-04-08
5.0.0	5 / 15	2021-04-01
4.1.0	5 / 20	2021-02-20
4.0.4	5 / 19	2020-06-26
4.0.3	5 / 19	2020-02-29
4.0.2	6 / 19	2020-02-20
4.0.1	6 / 19	2020-02-19
4.0.0	6 / 19	2020-02-19
3.0.1	6 / 16	2019-12-30
3.0.0	6 / 16	2019-12-21
2.0.1	6 / 16	2019-12-19
2.0.0	5 / 16	2019-12-18
1.5.3	5 / 16	2019-10-14
1.5.2	5 / 16	2019-08-28
1.5.1	5 / 16	2019-08-04
1.5.0	5 / 16	2019-06-04
1.4.10	5 / 16	2019-02-18
1.4.9	5 / 16	2019-02-18
1.4.8	5 / 16	2018-12-14
1.4.7	5 / 16	2018-12-09
1.4.6	5 / 16	2018-10-14
1.4.5	5 / 13	2018-09-14
1.4.4	5 / 13	2018-08-27
1.4.3	5 / 13	2018-08-14
1.4.2	5 / 13	2018-06-16
1.4.1	5 / 13	2018-06-03
1.4.0	5 / 13	2018-06-01
1.3.3	5 / 14	2018-04-19
1.3.2	5 / 14	2018-03-19
1.3.1	5 / 14	2018-03-15
1.3.0	5 / 14	2018-03-01
1.2.7	5 / 14	2018-02-27
1.2.6	5 / 14	2018-02-26
1.2.5	5 / 14	2018-02-11
1.2.4	5 / 14	2018-02-10
1.2.3	5 / 14	2018-02-09
1.2.2	5 / 14	2018-01-29
1.2.0	5 / 13	2017-10-23
1.1.1	5 / 13	2017-10-03
1.1.0	5 / 13	2017-09-18
1.0.1	4 / 13	2017-07-10
1.0.0	3 / 14	2017-07-10

v6.1.5

1 finding

LOW No provenance attestation provenance

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

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

1 finding

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. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.1

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.1

1 finding

LOW No provenance attestation provenance

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

v6.0.0

1 finding

LOW No provenance attestation provenance

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

v5.1.9

1 finding

LOW No provenance attestation provenance

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

v5.1.8

1 finding

LOW No provenance attestation provenance

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

v5.1.7

1 finding

LOW No provenance attestation provenance

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

v5.1.6

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: mrgnrdrck → fatso83 (on 2024-01-09) provenance

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

v5.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: fatso83 → mrgnrdrck (on 2023-10-20) provenance

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

v5.1.4

1 finding

LOW No provenance attestation provenance

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

v5.1.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: mrgnrdrck → fatso83 (on 2022-12-05) provenance

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

v5.1.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: fatso83 → mrgnrdrck (on 2022-11-07) provenance

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

v5.1.1

1 finding

LOW No provenance attestation provenance

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

v5.1.0

2 findings

HIGH Publisher changed: mrgnrdrck → fatso83 (on 2021-05-25) provenance

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

v5.0.4

1 finding

LOW No provenance attestation provenance

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

v5.0.3

1 finding

LOW No provenance attestation provenance

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

v5.0.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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