@lovelybunch/core
Core Coconut functionality
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @lovelybunch/core is not impersonating cors; name reflects its own project identity. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): nanoid is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.0.77 | 7 / 3 | |
| 1.0.76 | 7 / 3 | |
| 1.0.75 | 7 / 3 | |
| 1.0.74 | 6 / 3 | |
| 1.0.73 | 4 / 3 | |
| 1.0.72 | 4 / 3 | |
| 1.0.71 | 4 / 3 | |
| 1.0.70 | 4 / 3 | |
| 1.0.69 | 4 / 3 | |
| 1.0.68 | 4 / 3 | |
| 1.0.67 | 4 / 3 | |
| 1.0.66 | 4 / 3 | |
| 1.0.65 | 4 / 3 | |
| 1.0.64 | 4 / 3 | |
| 1.0.63 | 4 / 3 | |
| 1.0.62 | 4 / 3 | |
| 1.0.61 | 4 / 3 | |
| 1.0.60 | 4 / 3 | |
| 1.0.59 | 4 / 3 | |
| 1.0.58 | 4 / 3 | |
| 1.0.57 | 4 / 3 | |
| 1.0.56 | 4 / 3 | |
| 1.0.55 | 4 / 3 | |
| 1.0.54 | 4 / 3 | |
| 1.0.53 | 4 / 3 | |
| 1.0.52 | 4 / 3 | |
| 1.0.51 | 4 / 3 | |
| 1.0.50 | 4 / 3 | |
| 1.0.49 | 4 / 3 | |
| 1.0.48 | 4 / 3 | |
| 1.0.46 | 4 / 3 | |
| 1.0.43 | 4 / 3 | |
| 1.0.41 | 4 / 3 | |
| 1.0.39 | 4 / 3 | |
| 1.0.38 | 4 / 3 | |
| 1.0.37 | 4 / 3 | |
| 1.0.35 | 4 / 3 | |
| 1.0.34 | 4 / 3 | |
| 1.0.33 | 4 / 3 | |
| 1.0.32 | 4 / 3 | |
| 1.0.31 | 4 / 3 | |
| 1.0.30 | 4 / 3 | |
| 1.0.29 | 4 / 3 | |
| 1.0.28 | 4 / 3 | |
| 1.0.27 | 4 / 3 | |
| 1.0.26 | 4 / 3 | |
| 1.0.25 | 4 / 3 | |
| 1.0.24 | 4 / 3 | |
| 1.0.23 | 4 / 3 | |
| 1.0.22 | 4 / 3 | |
| 1.0.21 | 4 / 3 |
v1.0.77
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.57
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
2 findingsPackage name '@lovelybunch/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.