@magic/css
css in js
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@magic-modules/light-switch | AI (npm-metadata): Dev-only same-org GitHub dep, stable across this package's history. | ai | |
| npm-metadata | url-dep:@magic-modules/git-badges | AI (npm-metadata): Dev-only dep to author's own org, not runtime code. | ai | |
| npm-metadata | url-dep:@magic/core | AI (npm-metadata): Sibling devDependency in same author's monorepo. | ai | |
| npm-metadata | url-dep:@magic-modules/gitbadges | AI (npm-metadata): Sibling devDependency in same author's monorepo. | ai | |
| phantom-deps | phantom-dep:@magic-themes/docs | AI (phantom-deps): Likely used via build/docs tooling not scanned as import; consistent with monorepo docs package. | ai | |
| npm-metadata | url-dep:@magic-modules/pre | AI (npm-metadata): Sibling devDependency in same author's monorepo. | ai | |
| npm-metadata | url-dep:@magic-themes/docs | AI (npm-metadata): Sibling package in same author's monorepo ecosystem, consistent pattern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @magic/css is not a typosquat of 'cors'; stable FP. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @magic/css is not a typosquat of 'qs'; stable FP. | ai |
Versions (showing 51 of 72)
| Version | Deps | Published |
|---|---|---|
| 0.7.60 | 7 / 8 | |
| 0.7.59 | 7 / 8 | |
| 0.7.58 | 7 / 8 | |
| 0.7.57 | 7 / 8 | |
| 0.7.56 | 7 / 8 | |
| 0.7.55 | 7 / 8 | |
| 0.7.54 | 7 / 8 | |
| 0.7.53 | 7 / 8 | |
| 0.7.52 | 7 / 8 | |
| 0.7.51 | 7 / 8 | |
| 0.7.50 | 7 / 8 | |
| 0.7.49 | 7 / 8 | |
| 0.7.48 | 7 / 8 | |
| 0.7.47 | 7 / 8 | |
| 0.7.46 | 7 / 8 | |
| 0.7.45 | 7 / 8 | |
| 0.7.44 | 7 / 8 | |
| 0.7.43 | 7 / 8 | |
| 0.7.42 | 7 / 8 | |
| 0.7.41 | 7 / 8 | |
| 0.7.40 | 7 / 8 | |
| 0.7.39 | 7 / 8 | |
| 0.7.38 | 7 / 8 | |
| 0.7.37 | 7 / 8 | |
| 0.7.36 | 7 / 8 | |
| 0.7.35 | 6 / 8 | |
| 0.7.34 | 6 / 8 | |
| 0.7.33 | 6 / 8 | |
| 0.7.32 | 6 / 8 | |
| 0.7.31 | 6 / 8 | |
| 0.7.30 | 6 / 8 | |
| 0.7.29 | 6 / 8 | |
| 0.7.28 | 6 / 8 | |
| 0.7.27 | 6 / 8 | |
| 0.7.26 | 6 / 8 | |
| 0.7.25 | 6 / 8 | |
| 0.7.24 | 6 / 8 | |
| 0.7.23 | 6 / 8 | |
| 0.7.22 | 6 / 8 | |
| 0.7.21 | 6 / 8 | |
| 0.7.20 | 6 / 8 | |
| 0.7.19 | 6 / 8 | |
| 0.7.18 | 6 / 8 | |
| 0.7.17 | 7 / 7 | |
| 0.7.16 | 6 / 8 | |
| 0.7.15 | 6 / 8 | |
| 0.7.14 | 6 / 8 | |
| 0.7.13 | 6 / 8 | |
| 0.7.12 | 5 / 8 | |
| 0.7.11 | 5 / 8 | |
| 0.7.10 | 5 / 8 |
v0.7.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.