boxen
Create boxes in the terminal
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (term-size, type-fest) are both sindresorhus-authored packages consistent with boxen's terminal utility purpose; no malicious signal. | ai | |
| dependencies | unvetted-dep:term-size | AI (dependencies): term-size is a sindresorhus package used for terminal size detection; unvetted status is a pipeline artifact, not a risk indicator for this well-known package. | ai | |
| dependencies | unvetted-dep:filled-array | AI (dependencies): filled-array is a small sindresorhus utility; consistent with this package's ecosystem and author. Low risk, stable dependency. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus packages historically lack Sigstore provenance; this is a stable pattern for this publisher and not a risk indicator. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 8 / 4 | |
| 7.1.1 | 8 / 4 | |
| 7.1.0 | 8 / 4 | |
| 7.0.2 | 8 / 4 | |
| 7.0.1 | 8 / 4 | |
| 7.0.0 | 8 / 4 | |
| 6.2.1 | 8 / 5 | |
| 6.2.0 | 8 / 5 | |
| 6.1.0 | 8 / 5 | |
| 6.0.0 | 8 / 5 | |
| 5.1.2 | 8 / 4 | |
| 5.1.1 | 8 / 4 | |
| 5.1.0 | 8 / 4 | |
| 5.0.1 | 8 / 4 | |
| 5.0.0 | 8 / 4 | |
| 4.2.0 | 8 / 4 | |
| 4.1.0 | 8 / 4 | |
| 4.0.0 | 8 / 4 | |
| 3.2.0 | 8 / 4 | |
| 3.1.0 | 8 / 4 | |
| 3.0.0 | 7 / 4 | |
| 2.1.0 | 7 / 3 | |
| 2.0.0 | 7 / 3 | |
| 1.3.0 | 7 / 3 | |
| 1.2.2 | 7 / 3 | |
| 1.2.1 | 7 / 3 | |
| 1.2.0 | 7 / 3 | |
| 1.1.0 | 7 / 3 | |
| 1.0.0 | 7 / 2 | |
| 0.8.1 | 7 / 2 | |
| 0.8.0 | 6 / 2 | |
| 0.7.0 | 9 / 2 | |
| 0.6.0 | 9 / 2 | |
| 0.5.1 | 8 / 2 | |
| 0.5.0 | 8 / 2 | |
| 0.4.0 | 7 / 2 | |
| 0.3.1 | 6 / 2 | |
| 0.3.0 | 6 / 2 | |
| 0.2.0 | 6 / 2 | |
| 0.1.0 | 6 / 2 |
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
v0.1.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.