@archships/dim-agent-sdk
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@zenmux/ai-sdk-provider | AI (dependencies): Beta AI provider adapter matching package's multi-provider SDK purpose; no malicious indicators. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): UNLICENSED is a legal/IP concern, not a security risk; stable for this package. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.0.75 | 10 / 0 | |
| 0.0.74 | 10 / 0 | |
| 0.0.73 | 10 / 0 | |
| 0.0.72 | 10 / 0 | |
| 0.0.71 | 10 / 0 | |
| 0.0.70 | 10 / 0 | |
| 0.0.69 | 10 / 0 | |
| 0.0.68 | 10 / 0 | |
| 0.0.67 | 10 / 0 | |
| 0.0.66 | 10 / 0 | |
| 0.0.65 | 10 / 0 | |
| 0.0.64 | 10 / 0 | |
| 0.0.63 | 10 / 0 | |
| 0.0.62 | 10 / 0 | |
| 0.0.61 | 10 / 0 | |
| 0.0.60 | 10 / 0 | |
| 0.0.59 | 10 / 0 | |
| 0.0.58 | 10 / 0 | |
| 0.0.57 | 10 / 0 | |
| 0.0.56 | 10 / 0 | |
| 0.0.55 | 10 / 0 | |
| 0.0.54 | 10 / 0 | |
| 0.0.53 | 10 / 0 | |
| 0.0.52 | 10 / 0 | |
| 0.0.51 | 10 / 0 | |
| 0.0.50 | 10 / 0 | |
| 0.0.49 | 10 / 0 | |
| 0.0.48 | 10 / 0 | |
| 0.0.47 | 10 / 0 | |
| 0.0.46 | 10 / 0 | |
| 0.0.45 | 10 / 0 | |
| 0.0.44 | 10 / 0 | |
| 0.0.43 | 10 / 0 | |
| 0.0.42 | 10 / 0 | |
| 0.0.41 | 10 / 0 | |
| 0.0.40 | 10 / 0 | |
| 0.0.39 | 10 / 0 | |
| 0.0.38 | 10 / 0 | |
| 0.0.37 | 10 / 0 | |
| 0.0.36 | 10 / 0 | |
| 0.0.35 | 10 / 0 | |
| 0.0.34 | 10 / 0 | |
| 0.0.33 | 10 / 0 | |
| 0.0.32 | 10 / 0 | |
| 0.0.31 | 11 / 0 | |
| 0.0.30 | 11 / 0 | |
| 0.0.29 | 11 / 0 | |
| 0.0.28 | 11 / 0 | |
| 0.0.27 | 11 / 0 | |
| 0.0.26 | 11 / 0 | |
| 0.0.25 | 11 / 0 |
v0.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.