@yarn-tool/get-paths-by-type ISC 18 versions

@yarn-tool/get-paths-by-type

npm Repository Homepage

根據類型 Symbol 取得對應的路徑陣列（支援全域 npm/yarn 路徑） / Get corresponding path array based on type Symbol (supports global npm/yarn paths)

18

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

yarn-toolget-pathsglobal-dirsglobal-pathssymbolpath-resolvernpm-globalyarn-globalyarnnpmworkspacesmonoreponode-modulespackagespackage

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@yarn-tool/fnm-detect	AI (dependencies): First-party sibling package in the same bluelovers/ws-yarn-workspaces monorepo; unvetted flag is a routing artifact, not a genuine risk.	ai	2026/04/24
dependencies	unvetted-dep:@yarn-tool/get-global-dirs	AI (dependencies): First-party sibling package in the same bluelovers/ws-yarn-workspaces monorepo; unvetted flag is a routing artifact, not a genuine risk.	ai	2026/04/24
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared as a dependency and used implicitly via TS compilation. Stable benign pattern for this package.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
2.0.18	3 / 0	2026-04-26
2.0.17	3 / 0	2026-04-26
2.0.16	3 / 0	2026-03-12
2.0.14	3 / 0	2026-03-09
2.0.11	3 / 0	2026-03-02
2.0.10	2 / 0	2024-05-03
2.0.9	2 / 0	2022-12-09
2.0.8	2 / 0	2022-11-14
2.0.7	2 / 0	2022-10-01
2.0.6	2 / 0	2022-09-29
2.0.5	2 / 0	2022-09-27
2.0.4	2 / 0	2022-09-06
2.0.3	2 / 0	2022-08-26
2.0.2	2 / 0	2022-08-13
2.0.1	2 / 0	2022-07-31
2.0.0	2 / 0	2022-07-07
1.0.3	2 / 0	2022-05-11
1.0.2	2 / 0	2021-10-13

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

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.

v2.0.14

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.

v2.0.11

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.

v2.0.10

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.

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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