@amodalai/amodal
Amodal 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Declared and used; markdown parsing for CLI. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Declared and used; version comparison utility. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Declared and used; CLI output formatting dependency. | ai | |
| phantom-deps | phantom-dep:marked-terminal | AI (phantom-deps): Declared and used; terminal markdown rendering. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): All 25 hits are localhost (127.0.0.1) in test files simulating OAuth callbacks — not exfiltration. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env-spread is in a dev CLI command passing env to a child process — standard pattern for this type of tool. | ai |
Versions (showing 100 of 132)
| Version | Deps | Published |
|---|---|---|
| 0.3.96 | 14 / 6 | |
| 0.3.95 | 14 / 6 | |
| 0.3.94 | 14 / 6 | |
| 0.3.93 | 14 / 6 | |
| 0.3.92 | 14 / 6 | |
| 0.3.91 | 14 / 6 | |
| 0.3.90 | 15 / 6 | |
| 0.3.89 | 15 / 6 | |
| 0.3.88 | 15 / 6 | |
| 0.3.87 | 15 / 6 | |
| 0.3.86 | 15 / 6 | |
| 0.3.85 | 15 / 6 | |
| 0.3.84 | 15 / 6 | |
| 0.3.83 | 15 / 6 | |
| 0.3.82 | 15 / 6 | |
| 0.3.81 | 15 / 6 | |
| 0.3.80 | 15 / 6 | |
| 0.3.79 | 15 / 6 | |
| 0.3.78 | 15 / 6 | |
| 0.3.77 | 15 / 6 | |
| 0.3.76 | 15 / 6 | |
| 0.3.75 | 15 / 6 | |
| 0.3.74 | 15 / 6 | |
| 0.3.73 | 15 / 6 | |
| 0.3.72 | 15 / 6 | |
| 0.3.71 | 15 / 6 | |
| 0.3.70 | 15 / 6 | |
| 0.3.69 | 15 / 6 | |
| 0.3.68 | 15 / 6 | |
| 0.3.67 | 15 / 6 | |
| 0.3.66 | 15 / 6 | |
| 0.3.65 | 15 / 6 | |
| 0.3.64 | 15 / 6 | |
| 0.3.63 | 15 / 6 | |
| 0.3.62 | 15 / 6 | |
| 0.3.61 | 15 / 6 | |
| 0.3.60 | 15 / 6 | |
| 0.3.59 | 15 / 6 | |
| 0.3.58 | 15 / 6 | |
| 0.3.57 | 15 / 6 | |
| 0.3.56 | 15 / 6 | |
| 0.3.55 | 15 / 6 | |
| 0.3.54 | 15 / 6 | |
| 0.3.53 | 15 / 6 | |
| 0.3.52 | 15 / 6 | |
| 0.3.51 | 15 / 6 | |
| 0.3.50 | 15 / 6 | |
| 0.3.49 | 14 / 6 | |
| 0.3.48 | 14 / 6 | |
| 0.3.47 | 14 / 6 | |
| 0.3.46 | 14 / 6 | |
| 0.3.45 | 14 / 6 | |
| 0.3.44 | 14 / 6 | |
| 0.3.43 | 14 / 6 | |
| 0.3.42 | 14 / 6 | |
| 0.3.41 | 14 / 6 | |
| 0.3.40 | 14 / 6 | |
| 0.3.39 | 14 / 6 | |
| 0.3.38 | 14 / 6 | |
| 0.3.37 | 14 / 6 | |
| 0.3.36 | 14 / 6 | |
| 0.3.35 | 14 / 6 | |
| 0.3.34 | 14 / 6 | |
| 0.3.33 | 14 / 6 | |
| 0.3.32 | 14 / 6 | |
| 0.3.31 | 14 / 6 | |
| 0.3.30 | 14 / 6 | |
| 0.3.29 | 14 / 6 | |
| 0.3.28 | 14 / 6 | |
| 0.3.27 | 14 / 6 | |
| 0.3.26 | 14 / 6 | |
| 0.3.25 | 18 / 7 | |
| 0.3.24 | 18 / 7 | |
| 0.3.23 | 18 / 7 | |
| 0.3.22 | 18 / 7 | |
| 0.3.21 | 18 / 7 | |
| 0.3.20 | 18 / 7 | |
| 0.3.19 | 18 / 7 | |
| 0.3.18 | 18 / 7 | |
| 0.3.17 | 18 / 7 | |
| 0.3.16 | 18 / 7 | |
| 0.3.15 | 18 / 7 | |
| 0.3.14 | 18 / 7 | |
| 0.3.13 | 18 / 7 | |
| 0.3.12 | 18 / 7 | |
| 0.3.11 | 18 / 7 | |
| 0.3.10 | 18 / 7 | |
| 0.3.9 | 18 / 7 | |
| 0.3.8 | 18 / 7 | |
| 0.3.7 | 18 / 7 | |
| 0.3.6 | 18 / 7 | |
| 0.3.5 | 18 / 7 | |
| 0.3.4 | 18 / 7 | |
| 0.3.3 | 18 / 7 | |
| 0.3.2 | 18 / 7 | |
| 0.3.1 | 17 / 7 | |
| 0.3.0 | 17 / 7 | |
| 0.2.10 | 16 / 7 | |
| 0.2.9 | 16 / 7 | |
| 0.2.8 | 16 / 7 |
v0.3.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.