@magic/log
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped package @magic/log is not a typosquat of glob; Levenshtein noise on short names. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped package @magic/log is not a typosquat of koa; Levenshtein noise on short names. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @magic/log is not a typosquat of got; Levenshtein noise on short names. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @magic/log is not a typosquat of pg; Levenshtein noise on short names. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @magic/log is not a typosquat of joi; Levenshtein noise on short names. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @magic/log is not a typosquat of zod; Levenshtein noise on short names. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.1.23 | 1 / 10 | |
| 0.1.22 | 1 / 10 | |
| 0.1.21 | 1 / 10 | |
| 0.1.20 | 1 / 10 | |
| 0.1.19 | 1 / 10 | |
| 0.1.18 | 1 / 8 | |
| 0.1.17 | 1 / 8 | |
| 0.1.16 | 1 / 8 | |
| 0.1.15 | 1 / 8 | |
| 0.1.14 | 1 / 8 | |
| 0.1.13 | 1 / 8 | |
| 0.1.12 | 1 / 8 | |
| 0.1.11 | 1 / 8 | |
| 0.1.10 | 1 / 8 | |
| 0.1.9 | 1 / 8 | |
| 0.1.8 | 1 / 8 | |
| 0.1.7 | 1 / 8 | |
| 0.1.6 | 1 / 8 | |
| 0.1.5 | 1 / 8 | |
| 0.1.4 | 1 / 8 | |
| 0.1.3 | 1 / 7 | |
| 0.0.2 | 1 / 1 |
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.