@pnpm/resolving.bun-resolver No license 22 versions

@pnpm/resolving.bun-resolver

npm Repository Homepage

22

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pnpmuserzkochan

Keywords

pnpmpnpm10bunruntime

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): zkochan is the creator of pnpm with 3475 days of npm history and 202 approved packages. Transition from pnpmuser (bot account) to zkochan is a legitimate maintainer account change for this official pnpm monorepo package.	ai	2026/04/27
phantom-deps	phantom-dep:@pnpm/types	AI (phantom-deps): Same-org @pnpm scoped type-only dependency; phantom-dep false positive common in pnpm monorepo TypeScript packages.	ai	2026/04/25
phantom-deps	phantom-dep:@pnpm/fetcher-base	AI (phantom-deps): Same-org @pnpm scoped internal dependency; phantom-dep false positive common in pnpm monorepo TypeScript packages.	ai	2026/04/25
phantom-deps	phantom-dep:@pnpm/node.fetcher	AI (phantom-deps): Same-org @pnpm scoped internal dependency; phantom-dep false positive common in pnpm monorepo TypeScript packages.	ai	2026/04/25
phantom-deps	phantom-dep:@pnpm/fetching.binary-fetcher	AI (phantom-deps): Same-org @pnpm scoped internal dependency; phantom-dep false positive common in pnpm monorepo TypeScript packages.	ai	2026/04/25
phantom-deps	phantom-dep:semver	AI (phantom-deps): semver is a declared dependency used in config/type contexts; phantom-dep signal is a false positive for this package.	ai	2026/04/25

Versions (showing 22 of 22)

Version	Deps	Published
1005.0.13	12 / 3	2026-05-27
1005.0.12	12 / 3	2026-05-06
1005.0.11	12 / 3	2026-03-24
1005.0.10	12 / 3	2026-03-11
1005.0.9	12 / 3	2026-03-07
1005.0.8	12 / 3	2026-02-23
1005.0.7	12 / 3	2026-02-17
1005.0.6	12 / 3	2026-02-09
1005.0.5	12 / 3	2026-02-07
1005.0.4	12 / 3	2026-01-26
1005.0.3	12 / 3	2026-01-19
1005.0.2	12 / 3	2026-01-09
1005.0.1	12 / 3	2025-12-30
1005.0.0	12 / 3	2025-12-23
1004.0.0	12 / 3	2025-12-15
1003.0.2	12 / 3	2025-12-08
1003.0.1	12 / 3	2025-12-02
1003.0.0	12 / 3	2025-11-27
1002.0.4	12 / 3	2025-11-20
1002.0.3	12 / 3	2025-11-12
1002.0.2	12 / 3	2025-11-09
1002.0.1	12 / 3	2025-10-28

v1005.0.13

1 finding

LOW No provenance attestation provenance

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

v1005.0.12

1 finding

LOW No provenance attestation provenance

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

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

v1005.0.10

1 finding

LOW No provenance attestation provenance

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

v1005.0.9

1 finding

LOW No provenance attestation provenance

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

v1005.0.8

1 finding

LOW No provenance attestation provenance

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

v1005.0.7

2 findings

HIGH Publisher changed: pnpmuser → zkochan (on 2026-02-17) provenance

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

v1005.0.6

1 finding

LOW No provenance attestation provenance

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

v1005.0.5

1 finding

LOW No provenance attestation provenance

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

v1005.0.4

1 finding

LOW No provenance attestation provenance

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

v1005.0.3

1 finding

LOW No provenance attestation provenance

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

v1005.0.2

1 finding

LOW No provenance attestation provenance

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

v1005.0.1

1 finding

LOW No provenance attestation provenance

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

v1005.0.0

1 finding

LOW No provenance attestation provenance

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

v1004.0.0

1 finding

LOW No provenance attestation provenance

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

v1003.0.2

1 finding

LOW No provenance attestation provenance

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

v1003.0.1

2 findings

HIGH Publisher changed: pnpmuser → zkochan (on 2025-12-02) provenance

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

v1003.0.0

1 finding

LOW No provenance attestation provenance

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

v1002.0.4

1 finding

LOW No provenance attestation provenance

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

v1002.0.3

1 finding

LOW No provenance attestation provenance

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

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

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