← Home

@pnpm/package-is-installable

npm Repository Homepage

Checks if a package is installable on the current system

12
Versions
MIT
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

pnpmpnpm10

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@pnpm/core-loggers AI (dependencies): Internal pnpm monorepo package from the same org; expected dependency for this pnpm utility. Stable across versions. ai
dependencies unvetted-dep:@pnpm/env.system-node-version AI (dependencies): Internal pnpm monorepo package from the same org; expected dependency for this pnpm utility. Stable across versions. ai
phantom-deps phantom-dep:mem AI (phantom-deps): Declared dependency used in pnpm's installability checks; phantom detection is a false positive for this package's usage pattern. ai
phantom-deps phantom-dep:execa AI (phantom-deps): Aliased to safe-execa as a deliberate security measure; phantom detection is a false positive here. ai
phantom-deps phantom-dep:@pnpm/cli-meta AI (phantom-deps): Same-org pnpm package; phantom detection is a false positive for this monorepo package's usage pattern. ai

Versions (showing 12 of 12)

Version Deps Published
1000.0.21 9 / 4
1000.0.20 9 / 4
1000.0.19 9 / 4
1000.0.18 9 / 4
1000.0.17 9 / 4
1000.0.16 9 / 4
1000.0.15 9 / 4
1000.0.14 9 / 4
1000.0.13 9 / 4
1000.0.12 9 / 3
1000.0.11 9 / 3
1000.0.10 9 / 3

v1000.0.21

1 finding
LOW No provenance attestation provenance

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

v1000.0.20

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.

v1000.0.19

1 finding
LOW No provenance attestation provenance

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

v1000.0.18

1 finding
LOW No provenance attestation provenance

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

v1000.0.17

1 finding
LOW No provenance attestation provenance

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

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

v1000.0.15

1 finding
LOW No provenance attestation provenance

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

v1000.0.14

1 finding
LOW No provenance attestation provenance

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

v1000.0.13

1 finding
LOW No provenance attestation provenance

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

v1000.0.12

1 finding
LOW No provenance attestation provenance

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

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

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