@decaf-ts/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, 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cli.cjs | AI (source-diff): Rollup UMD bundle, not obfuscation; matches documented CLI dynamic-loader behavior. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped CLI package; name similarity to joi is coincidental, not a typosquat. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Used in a file-loader utility (loadFromFile); stable pattern for this CLI package. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 2 / 2 | |
| 0.11.2 | 2 / 2 | |
| 0.11.1 | 2 / 2 | |
| 0.11.0 | 2 / 2 | |
| 0.10.2 | 2 / 2 | |
| 0.10.1 | 2 / 2 | |
| 0.10.0 | 2 / 2 | |
| 0.9.0 | 2 / 2 | |
| 0.8.0 | 2 / 2 | |
| 0.7.0 | 2 / 2 | |
| 0.6.0 | 2 / 2 | |
| 0.5.7 | 2 / 2 | |
| 0.5.6 | 2 / 2 | |
| 0.5.5 | 2 / 2 | |
| 0.5.4 | 2 / 2 | |
| 0.5.3 | 2 / 2 | |
| 0.5.2 | 2 / 2 | |
| 0.5.1 | 2 / 2 | |
| 0.5.0 | 2 / 2 | |
| 0.4.17 | 2 / 2 | |
| 0.4.16 | 2 / 2 | |
| 0.4.15 | 2 / 2 | |
| 0.4.14 | 2 / 2 | |
| 0.4.13 | 2 / 2 | |
| 0.4.12 | 2 / 2 | |
| 0.4.11 | 2 / 2 | |
| 0.4.9 | 1 / 2 | |
| 0.4.8 | 1 / 2 | |
| 0.4.7 | 1 / 1 | |
| 0.4.6 | 1 / 1 | |
| 0.4.5 | 1 / 1 | |
| 0.4.4 | 1 / 1 | |
| 0.4.3 | 1 / 1 | |
| 0.4.2 | 1 / 1 | |
| 0.4.1 | 1 / 1 | |
| 0.4.0 | 1 / 1 | |
| 0.3.9 | 1 / 26 | |
| 0.3.8 | 1 / 31 | |
| 0.3.7 | 1 / 31 | |
| 0.3.6 | 1 / 31 | |
| 0.3.5 | 1 / 31 | |
| 0.3.2 | 1 / 31 | |
| 0.3.0 | 1 / 31 | |
| 0.0.14 | 1 / 37 | |
| 0.0.12 | 1 / 37 | |
| 0.0.11 | 1 / 37 | |
| 0.0.10 | 1 / 37 | |
| 0.0.9 | 1 / 37 | |
| 0.0.8 | 1 / 37 | |
| 0.0.7 | 1 / 36 | |
| 0.0.5 | 1 / 36 | |
| 0.0.2 | 1 / 36 |
v0.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.
v0.3.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.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.