@thi.ng/meta-css
Data-driven CSS framework codegen, transpiler & bundler
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@thi.ng/api | AI (phantom-deps): Monorepo package; deps may be used transitively or re-exported, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:@thi.ng/args | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/arrays | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/checks | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/errors | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/logger | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/compare | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/file-io | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/memoize | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/rstream | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/strings | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/hiccup-css | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/text-format | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@thi.ng/transducers | AI (phantom-deps): Same @thi.ng monorepo; phantom-dep heuristic unreliable for bundled packages. | ai |
Versions (showing 69 of 69)
| Version | Deps | Published |
|---|---|---|
| 0.19.69 | 14 / 4 | |
| 0.19.68 | 14 / 4 | |
| 0.19.67 | 14 / 4 | |
| 0.19.65 | 14 / 4 | |
| 0.19.64 | 14 / 4 | |
| 0.19.62 | 14 / 4 | |
| 0.19.61 | 14 / 4 | |
| 0.19.60 | 14 / 4 | |
| 0.19.59 | 14 / 4 | |
| 0.19.58 | 14 / 4 | |
| 0.19.57 | 14 / 4 | |
| 0.19.56 | 14 / 4 | |
| 0.19.55 | 14 / 4 | |
| 0.19.54 | 14 / 4 | |
| 0.19.53 | 14 / 4 | |
| 0.19.52 | 14 / 4 | |
| 0.19.51 | 14 / 4 | |
| 0.19.50 | 14 / 4 | |
| 0.19.49 | 14 / 4 | |
| 0.19.48 | 14 / 4 | |
| 0.19.46 | 14 / 4 | |
| 0.19.45 | 14 / 4 | |
| 0.19.44 | 14 / 4 | |
| 0.19.43 | 14 / 4 | |
| 0.19.42 | 14 / 4 | |
| 0.19.41 | 14 / 4 | |
| 0.19.40 | 14 / 4 | |
| 0.19.39 | 14 / 4 | |
| 0.19.38 | 14 / 4 | |
| 0.19.37 | 14 / 4 | |
| 0.19.36 | 14 / 4 | |
| 0.19.35 | 14 / 4 | |
| 0.19.34 | 14 / 4 | |
| 0.19.30 | 14 / 4 | |
| 0.19.29 | 14 / 4 | |
| 0.19.28 | 14 / 4 | |
| 0.19.27 | 14 / 4 | |
| 0.19.26 | 14 / 4 | |
| 0.19.25 | 14 / 4 | |
| 0.19.24 | 14 / 4 | |
| 0.19.23 | 14 / 4 | |
| 0.19.22 | 14 / 4 | |
| 0.19.21 | 14 / 4 | |
| 0.19.20 | 14 / 4 | |
| 0.19.18 | 14 / 4 | |
| 0.19.17 | 14 / 4 | |
| 0.19.16 | 14 / 4 | |
| 0.19.15 | 14 / 4 | |
| 0.19.14 | 14 / 4 | |
| 0.19.13 | 14 / 4 | |
| 0.19.12 | 14 / 4 | |
| 0.19.11 | 14 / 4 | |
| 0.19.10 | 14 / 4 | |
| 0.19.9 | 14 / 4 | |
| 0.19.8 | 14 / 4 | |
| 0.19.7 | 14 / 4 | |
| 0.19.6 | 14 / 4 | |
| 0.19.5 | 14 / 4 | |
| 0.19.4 | 14 / 4 | |
| 0.19.3 | 14 / 4 | |
| 0.19.2 | 14 / 4 | |
| 0.19.1 | 14 / 4 | |
| 0.19.0 | 14 / 4 | |
| 0.18.15 | 14 / 4 | |
| 0.18.14 | 14 / 4 | |
| 0.18.13 | 14 / 4 | |
| 0.18.12 | 14 / 4 | |
| 0.18.11 | 14 / 4 | |
| 0.18.10 | 14 / 4 |
v0.19.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.