@parcel/reporter-cli
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Parcel monorepo publishes in coordinated batches; dormancy between releases is normal for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): term-size is a well-known Sindre Sorhus utility for terminal size detection — a natural fit for a CLI reporter. Addition is benign and intentional. | ai | |
| dependencies | unvetted-dep:term-size | AI (dependencies): term-size is a well-known, legitimate utility package for terminal size detection; its use in a CLI reporter is expected and stable across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package from the official Parcel bundler; missing description is a consistent pattern across the @parcel/* namespace, not a malicious signal. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread provenance adoption; published by a long-standing trusted maintainer from the official Parcel monorepo. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.16.4 | 5 / 6 | |
| 2.16.3 | 5 / 6 | |
| 2.9.2 | 5 / 5 | |
| 2.9.1 | 5 / 5 | |
| 2.9.0 | 5 / 5 | |
| 2.8.3 | 5 / 6 | |
| 2.8.2 | 5 / 6 | |
| 2.8.1 | 5 / 6 | |
| 2.8.0 | 5 / 6 | |
| 2.7.0 | 5 / 6 | |
| 2.6.2 | 5 / 6 | |
| 2.6.1 | 5 / 6 | |
| 2.5.0 | 5 / 6 | |
| 2.4.1 | 5 / 6 | |
| 2.4.0 | 5 / 6 | |
| 2.3.2 | 4 / 7 | |
| 2.3.1 | 4 / 7 | |
| 2.3.0 | 4 / 7 | |
| 2.2.1 | 11 / 0 | |
| 2.2.0 | 11 / 0 | |
| 2.1.1 | 11 / 0 | |
| 2.1.0 | 11 / 0 | |
| 2.0.1 | 11 / 0 |
v2.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.