@hanzogui/generate-themes
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Tool loads user-supplied theme config files at runtime; dynamic require of inputFilePath is intentional and documented behavior. | ai | |
| phantom-deps | phantom-dep:@hanzogui/types | AI (phantom-deps): Same-org type-only dependency; not directly imported but used for type declarations. | ai | |
| phantom-deps | phantom-dep:@hanzogui/create-theme | AI (phantom-deps): Same-org sibling package; may be re-exported or used indirectly through build pipeline. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 5 / 1 | |
| 4.4.0 | 5 / 1 | |
| 4.3.1 | 5 / 1 | |
| 3.0.6 | 5 / 1 | |
| 3.0.5 | 5 / 1 | |
| 3.0.2 | 5 / 1 | |
| 3.0.1 | 5 / 1 | |
| 3.0.0 | 5 / 1 | |
| 2.0.5 | 5 / 1 | |
| 2.0.4 | 5 / 1 | |
| 2.0.3 | 5 / 1 | |
| 2.0.2 | 5 / 1 | |
| 2.0.1 | 5 / 1 | |
| 2.0.0 | 5 / 1 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.