upath2 ISC 29 versions

upath2

npm Repository Homepage

A proxy to `path`, replacing `\` with `/` for all results

29

Versions

ISC

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

bluelovers

Keywords

absolutebackslashcheckcoredetectdirfilefilepathfixforwardfpfsisis-absoluteisabsolutenormalizepathpathssepshimslashslashestrailingunixurixutilutilswin32windows

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:core.js	AI (source-diff): core.js is readable TypeScript-compiled output wrapping Node's path module; long lines from transpilation, not obfuscation.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established publisher with strong track record; lack of provenance is informational, not a risk signal for this package.	ai	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
3.1.23	5 / 1	2026-03-02
3.1.22	5 / 1	2026-03-01
3.1.20	4 / 1	2024-08-29
3.1.19	4 / 1	2022-10-02
3.1.18	4 / 1	2022-09-29
3.1.16	4 / 1	2022-09-28
3.1.15	4 / 1	2022-08-11
3.1.13	4 / 1	2022-05-11
3.1.12	3 / 1	2021-12-29
3.1.11	4 / 1	2021-12-29
3.1.10	4 / 1	2021-08-13
3.1.9	4 / 1	2021-07-08
3.1.8	3 / 1	2021-06-16
3.1.7	3 / 1	2021-02-12
3.1.6	3 / 1	2020-08-08
3.1.5	3 / 1	2020-07-05
3.1.4	3 / 1	2020-06-25
3.1.3	0 / 1	2020-06-25
3.0.6	0 / 1	2020-06-16
3.0.5	0 / 1	2020-06-09
3.0.4	1 / 1	2020-06-09
3.0.2	0 / 0	2020-06-09
2.1.3	0 / 2	2018-11-02
2.1.2	0 / 0	2018-03-30
2.1.0	1 / 2	2017-12-10
2.0.0	1 / 3	2017-12-09
1.0.2	0 / 3	2016-04-10
1.0.1	0 / 2	2016-04-06
1.0.0	0 / 2	2016-04-06

v3.1.23

1 finding

LOW No provenance attestation provenance

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

v3.1.22

1 finding

LOW No provenance attestation provenance

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

v3.1.20

1 finding

LOW No provenance attestation provenance

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

v3.1.19

1 finding

LOW No provenance attestation provenance

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

v3.1.18

1 finding

LOW No provenance attestation provenance

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

v3.1.16

1 finding

LOW No provenance attestation provenance

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

v3.1.15

1 finding

LOW No provenance attestation provenance

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

v3.1.13

1 finding

LOW No provenance attestation provenance

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

v3.1.12

1 finding

LOW No provenance attestation provenance

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

v3.1.11

1 finding

LOW No provenance attestation provenance

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

v3.1.10

1 finding

LOW No provenance attestation provenance

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

v3.1.9

1 finding

LOW No provenance attestation provenance

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

v3.1.8

1 finding

LOW No provenance attestation provenance

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

v3.1.7

1 finding

LOW No provenance attestation provenance

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

v3.1.6

1 finding

LOW No provenance attestation provenance

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

v3.1.5

1 finding

LOW No provenance attestation provenance

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

v3.1.4

1 finding

LOW No provenance attestation provenance

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

v3.1.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.6

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

2 findings

HIGH New obfuscated file: core.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.

LOW No provenance attestation provenance

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