@codelet/core
mini core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 miniprogram package with 44 versions; name collision with 'cors' is purely coincidental. | ai | |
| phantom-deps | phantom-dep:miniprogram-api-typings | AI (phantom-deps): Type-only dependency for WeChat miniprogram typings; not directly imported at runtime. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.0.53 | 2 / 2 | |
| 0.0.52 | 2 / 2 | |
| 0.0.51 | 2 / 2 | |
| 0.0.50 | 2 / 2 | |
| 0.0.49 | 2 / 2 | |
| 0.0.48 | 2 / 2 | |
| 0.0.47 | 2 / 2 | |
| 0.0.46 | 2 / 2 | |
| 0.0.45 | 2 / 2 | |
| 0.0.44 | 2 / 2 | |
| 0.0.43 | 2 / 2 | |
| 0.0.42 | 2 / 2 | |
| 0.0.41 | 2 / 2 | |
| 0.0.40 | 2 / 2 | |
| 0.0.39 | 2 / 2 | |
| 0.0.38 | 2 / 2 | |
| 0.0.37 | 2 / 2 | |
| 0.0.36 | 2 / 2 | |
| 0.0.35 | 2 / 2 | |
| 0.0.34 | 2 / 2 | |
| 0.0.33 | 2 / 2 | |
| 0.0.32 | 2 / 2 | |
| 0.0.31 | 2 / 2 | |
| 0.0.30 | 2 / 2 | |
| 0.0.29 | 2 / 2 | |
| 0.0.28 | 2 / 2 | |
| 0.0.27 | 2 / 2 | |
| 0.0.26 | 2 / 2 | |
| 0.0.25 | 2 / 2 | |
| 0.0.24 | 2 / 2 | |
| 0.0.23 | 2 / 2 | |
| 0.0.22 | 2 / 2 | |
| 0.0.21 | 2 / 2 | |
| 0.0.20 | 2 / 2 | |
| 0.0.19 | 2 / 2 | |
| 0.0.18 | 2 / 2 | |
| 0.0.17 | 2 / 2 | |
| 0.0.16 | 2 / 2 | |
| 0.0.15 | 2 / 2 | |
| 0.0.14 | 3 / 1 | |
| 0.0.13 | 3 / 1 | |
| 0.0.12 | 3 / 1 | |
| 0.0.11 | 3 / 1 | |
| 0.0.10 | 3 / 1 | |
| 0.0.9 | 3 / 1 | |
| 0.0.8 | 3 / 1 | |
| 0.0.7 | 3 / 1 | |
| 0.0.6 | 3 / 1 | |
| 0.0.5 | 3 / 1 | |
| 0.0.4 | 3 / 1 | |
| 0.0.3 | 2 / 2 | |
| 0.0.2 | 3 / 2 | |
| 0.0.1 | 3 / 2 |
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.