beachball
The Sunniest Semantic Version Bumper
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:p-graph | AI (dependencies): p-graph is a legitimate task-graph library used intentionally by beachball for parallel publishing; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into execa options for npm CLI calls is standard and intentional for this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2.65.5 | 10 / 13 | |
| 2.65.4 | 10 / 13 | |
| 2.65.1 | 10 / 13 | |
| 2.64.3 | 10 / 27 | |
| 2.64.2 | 10 / 27 | |
| 2.64.0 | 10 / 27 | |
| 2.63.1 | 10 / 28 | |
| 2.63.0 | 10 / 28 | |
| 2.62.0 | 11 / 29 | |
| 2.61.0 | 11 / 29 | |
| 2.60.1 | 11 / 23 | |
| 2.60.0 | 11 / 23 | |
| 2.58.0 | 11 / 23 | |
| 2.56.0 | 12 / 24 | |
| 2.55.1 | 12 / 24 | |
| 2.55.0 | 12 / 24 | |
| 2.54.0 | 12 / 24 | |
| 2.53.0 | 12 / 24 | |
| 2.52.0 | 12 / 24 | |
| 2.51.2 | 12 / 24 | |
| 2.51.1 | 12 / 24 | |
| 2.51.0 | 12 / 24 | |
| 2.50.1 | 12 / 24 | |
| 2.50.0 | 12 / 24 | |
| 2.49.1 | 12 / 27 | |
| 2.49.0 | 12 / 27 | |
| 2.48.0 | 13 / 26 | |
| 2.47.1 | 12 / 26 | |
| 2.47.0 | 12 / 26 | |
| 2.46.0 | 12 / 26 | |
| 2.45.0 | 12 / 26 | |
| 2.44.1 | 12 / 26 | |
| 2.44.0 | 12 / 26 |
v2.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.50.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.