@magic/css AGPL-3.0 72 versions

@magic/css

npm Repository Homepage

css in js

72

Versions

AGPL-3.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jaschajaeh

Keywords

css-in-jscssmagic

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	2026/07/23
npm-metadata	url-dep:@magic-modules/git-badges	AI (npm-metadata): Dev-only dep to author's own org, not runtime code.	ai	2026/07/23
npm-metadata	url-dep:@magic/core	AI (npm-metadata): Sibling devDependency in same author's monorepo.	ai	2026/07/23
npm-metadata	url-dep:@magic-modules/gitbadges	AI (npm-metadata): Sibling devDependency in same author's monorepo.	ai	2026/07/23
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	2026/07/23
npm-metadata	url-dep:@magic-modules/pre	AI (npm-metadata): Sibling devDependency in same author's monorepo.	ai	2026/07/23
npm-metadata	url-dep:@magic-themes/docs	AI (npm-metadata): Sibling package in same author's monorepo ecosystem, consistent pattern.	ai	2026/07/23
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped @magic/css is not a typosquat of 'cors'; stable FP.	ai	2026/05/16
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @magic/css is not a typosquat of 'qs'; stable FP.	ai	2026/05/16

Versions (showing 72 of 72)

Version	Deps	Published
0.7.60	7 / 8	2026-06-28
0.7.59	7 / 8	2026-06-06
0.7.58	7 / 8	2026-05-07
0.7.57	7 / 8	2026-04-27
0.7.56	7 / 8	2024-07-24
0.7.55	7 / 8	2023-10-04
0.7.54	7 / 8	2023-02-16
0.7.53	7 / 8	2023-01-05
0.7.52	7 / 8	2022-05-14
0.7.51	7 / 8	2022-05-14
0.7.50	7 / 8	2022-04-06
0.7.49	7 / 8	2022-04-01
0.7.48	7 / 8	2021-12-26
0.7.47	7 / 8	2021-12-26
0.7.46	7 / 8	2021-12-24
0.7.45	7 / 8	2021-12-22
0.7.44	7 / 8	2021-12-21
0.7.43	7 / 8	2021-12-21
0.7.42	7 / 8	2021-12-06
0.7.41	7 / 8	2021-12-04
0.7.40	7 / 8	2021-09-24
0.7.39	7 / 8	2021-09-23
0.7.38	7 / 8	2021-09-01
0.7.37	7 / 8	2021-07-24
0.7.36	7 / 8	2021-07-11
0.7.35	6 / 8	2021-07-11
0.7.34	6 / 8	2021-07-10
0.7.33	6 / 8	2021-07-08
0.7.32	6 / 8	2021-04-29
0.7.31	6 / 8	2021-02-20
0.7.30	6 / 8	2021-02-11
0.7.29	6 / 8	2021-02-07
0.7.28	6 / 8	2021-01-17
0.7.27	6 / 8	2021-01-17
0.7.26	6 / 8	2021-01-05
0.7.25	6 / 8	2020-12-10
0.7.24	6 / 8	2020-11-22
0.7.23	6 / 8	2020-10-27
0.7.22	6 / 8	2020-10-06
0.7.21	6 / 8	2020-10-06
0.7.20	6 / 8	2020-10-05
0.7.19	6 / 8	2020-08-28
0.7.18	6 / 8	2020-07-16
0.7.17	7 / 7	2020-07-16
0.7.16	6 / 8	2020-06-22
0.7.15	6 / 8	2020-06-11
0.7.14	6 / 8	2020-05-25
0.7.13	6 / 8	2020-05-07
0.7.12	5 / 8	2020-05-03
0.7.11	5 / 8	2020-04-08
0.7.10	5 / 8	2020-02-23
0.7.9	5 / 8	2020-01-06
0.7.8	5 / 7	2020-01-02
0.7.7	5 / 7	2020-01-01
0.7.6	5 / 7	2019-12-07
0.7.4	5 / 6	2019-11-19
0.7.3	4 / 6	2019-11-18
0.7.2	4 / 6	2019-11-17
0.7.1	4 / 6	2019-06-07
0.7.0	4 / 5	2019-05-15
0.5.0	4 / 5	2019-05-10
0.4.6	5 / 4	2019-05-02
0.4.4	5 / 4	2019-04-25
0.4.3	4 / 1	2019-04-20
0.4.2	4 / 1	2019-04-18
0.4.1	4 / 1	2019-04-01
0.4.0	4 / 1	2019-04-01
0.3.0	4 / 1	2019-01-29
0.2.0	2 / 1	2019-01-29
0.1.0	2 / 1	2019-01-12
0.0.2	2 / 1	2018-12-12
0.0.1	2 / 1	2018-12-12

v0.7.60

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.59

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.56

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.54

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.53

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.52

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.51

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.49

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.48

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.47

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.45

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.6

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jaeh → jascha (on 2019-12-07, known maintainer) provenance

This version was published by a different npm account (jascha) than the most recent previously approved version (jaeh) on 2019-12-07, but jascha is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jascha → jaeh (on 2019-01-29, known maintainer) provenance

This version was published by a different npm account (jaeh) than the most recent previously approved version (jascha) on 2019-01-29, but jaeh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jascha → jaeh (on 2019-01-12, known maintainer) provenance

This version was published by a different npm account (jaeh) than the most recent previously approved version (jascha) on 2019-01-12, but jaeh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.