← Home

parcel

npm Repository Homepage
10
Versions
—
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

devongovett

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@parcel/reporter-cli AI (phantom-deps): Config-referenced plugin; not directly imported by design in Parcel's architecture. ai
phantom-deps phantom-dep:@parcel/package-manager AI (phantom-deps): Config-referenced plugin; not directly imported by design in Parcel's architecture. ai
phantom-deps phantom-dep:@parcel/reporter-tracer AI (phantom-deps): Config-referenced plugin; not directly imported by design in Parcel's architecture. ai
phantom-deps phantom-dep:@parcel/reporter-dev-server AI (phantom-deps): Config-referenced plugin; not directly imported by design in Parcel's architecture. ai

Versions (showing 10 of 10)

Version Deps Published
2.16.4 15 / 2
2.16.3 15 / 2
2.16.2 15 / 2
2.16.1 15 / 2
2.16.0 15 / 2
2.15.4 15 / 2
2.15.3 15 / 2
2.15.2 15 / 2
2.15.1 15 / 2
2.15.0 15 / 2

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

1 finding
LOW No provenance attestation provenance

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

v2.16.0

1 finding
LOW No provenance attestation provenance

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

v2.15.4

1 finding
LOW No provenance attestation provenance

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

v2.15.3

1 finding
LOW No provenance attestation provenance

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

v2.15.2

1 finding
LOW No provenance attestation provenance

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

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