@styleframe/cli
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/export-BMneJTdq.cjs | AI (source-diff): Bundled CLI output using node:fs/promises for file I/O; no network fetch or dynamic eval — false positive for this package. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop explained by extraction of code into @styleframe/dtcg dependency; not a stub/redirect. | ai | |
| source-diff | net-exec-file:dist/export-Cx6awh55.js | AI (source-diff): ESM counterpart of the same bundled CLI output; same false-positive reasoning applies. | ai | |
| source-diff | obfuscated-file:dist/index-BX6dI2z2.js | AI (source-diff): Standard webpack/rollup bundle output (jiti/mlly bundled); minification is expected for this CLI package. | ai | |
| source-diff | obfuscated-file:dist/build-aC0xw4RW.js | AI (source-diff): Bundled build artifact (webpack/rollup output of jiti+deps); long lines are minification, not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:@styleframe/loader | AI (phantom-deps): Same-org runtime dep; CLI tools commonly invoke dependencies without static top-level imports. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @styleframe/cli vs 'joi' is not a credible typosquat; edit-distance match is coincidental. | ai | |
| phantom-deps | phantom-dep:@styleframe/figma | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages that may be used indirectly. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 5 / 13 | |
| 3.0.0 | 4 / 13 | |
| 2.4.0 | 4 / 13 | |
| 2.3.2 | 3 / 13 | |
| 2.3.1 | 3 / 13 | |
| 2.2.0 | 3 / 13 | |
| 2.1.0 | 3 / 13 | |
| 2.0.3 | 4 / 10 | |
| 2.0.2 | 4 / 10 | |
| 2.0.1 | 4 / 10 | |
| 2.0.0 | 4 / 10 | |
| 1.0.5 | 4 / 10 | |
| 1.0.4 | 4 / 10 | |
| 1.0.3 | 4 / 10 |
v4.0.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.