@lovelybunch/cli
Command-line interface for Coconut
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lovelybunch/types | AI (phantom-deps): Same org scope; likely used transitively or via type-only imports not caught by the heuristic. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @lovelybunch/cli is a CLI tool unrelated to joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:fuse.js | AI (phantom-deps): fuse.js is declared in package.json dependencies; phantom-dep heuristic misfired on this package. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.0.77 | 12 / 6 | |
| 1.0.76 | 12 / 6 | |
| 1.0.75 | 13 / 7 | |
| 1.0.74 | 12 / 6 | |
| 1.0.73 | 12 / 6 | |
| 1.0.72 | 12 / 6 | |
| 1.0.71 | 11 / 6 | |
| 1.0.70 | 11 / 6 | |
| 1.0.69 | 11 / 6 | |
| 1.0.68 | 11 / 6 | |
| 1.0.67 | 11 / 6 | |
| 1.0.66 | 11 / 6 | |
| 1.0.65 | 11 / 6 | |
| 1.0.64 | 11 / 6 | |
| 1.0.63 | 11 / 6 | |
| 1.0.62 | 11 / 6 | |
| 1.0.61 | 11 / 6 | |
| 1.0.60 | 11 / 6 | |
| 1.0.59 | 11 / 6 | |
| 1.0.58 | 11 / 6 | |
| 1.0.57 | 11 / 6 | |
| 1.0.56 | 11 / 6 | |
| 1.0.55 | 11 / 6 | |
| 1.0.54 | 11 / 6 | |
| 1.0.53 | 11 / 6 | |
| 1.0.52 | 9 / 4 | |
| 1.0.51 | 9 / 4 | |
| 1.0.50 | 9 / 4 | |
| 1.0.49 | 9 / 4 | |
| 1.0.48 | 9 / 4 | |
| 1.0.47 | 9 / 4 | |
| 1.0.46 | 9 / 4 | |
| 1.0.43 | 9 / 4 | |
| 1.0.41 | 9 / 4 | |
| 1.0.39 | 9 / 4 | |
| 1.0.38 | 9 / 4 | |
| 1.0.37 | 9 / 4 | |
| 1.0.35 | 9 / 4 | |
| 1.0.34 | 9 / 4 | |
| 1.0.33 | 9 / 4 | |
| 1.0.32 | 9 / 4 | |
| 1.0.31 | 9 / 4 | |
| 1.0.30 | 9 / 4 | |
| 1.0.29 | 9 / 4 | |
| 1.0.28 | 9 / 4 | |
| 1.0.27 | 9 / 4 | |
| 1.0.26 | 9 / 4 | |
| 1.0.24 | 9 / 4 | |
| 1.0.23 | 9 / 4 | |
| 1.0.22 | 9 / 4 | |
| 1.0.21 | 9 / 4 | |
| 1.0.20 | 9 / 4 | |
| 1.0.18 | 9 / 4 | |
| 1.0.15 | 9 / 4 | |
| 1.0.14 | 9 / 4 | |
| 1.0.13 | 9 / 4 | |
| 1.0.12 | 9 / 4 | |
| 1.0.10 | 9 / 4 | |
| 1.0.9 | 9 / 4 | |
| 1.0.8 | 9 / 4 | |
| 1.0.7 | 9 / 4 |
v1.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.