@agentdock/crypto
E2E encryption for AgentDock — AES-256-GCM, key derivation, Web Crypto API
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped @agentdock/crypto is an AgentDock internal crypto utility, not a typosquat of bcrypt. | ai | |
| phantom-deps | phantom-dep:@agentdock/wire | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 2 / 3 | |
| 0.4.0 | 2 / 3 | |
| 0.0.72 | 3 / 3 | |
| 0.0.71 | 3 / 3 | |
| 0.0.70 | 3 / 3 | |
| 0.0.69 | 3 / 3 | |
| 0.0.68 | 3 / 3 | |
| 0.0.67 | 3 / 3 | |
| 0.0.66 | 3 / 3 | |
| 0.0.65 | 3 / 3 | |
| 0.0.64 | 3 / 3 | |
| 0.0.63 | 3 / 3 | |
| 0.0.62 | 3 / 3 | |
| 0.0.61 | 3 / 3 | |
| 0.0.60 | 2 / 3 | |
| 0.0.59 | 2 / 3 | |
| 0.0.58 | 2 / 3 | |
| 0.0.57 | 2 / 3 | |
| 0.0.56 | 2 / 3 | |
| 0.0.55 | 2 / 3 | |
| 0.0.54 | 2 / 3 | |
| 0.0.53 | 2 / 3 | |
| 0.0.52 | 2 / 3 | |
| 0.0.51 | 2 / 3 | |
| 0.0.50 | 2 / 3 | |
| 0.0.49 | 2 / 3 | |
| 0.0.48 | 2 / 3 | |
| 0.0.47 | 2 / 3 | |
| 0.0.46 | 2 / 3 | |
| 0.0.45 | 2 / 3 | |
| 0.0.44 | 2 / 3 | |
| 0.0.43 | 2 / 3 | |
| 0.0.42 | 2 / 3 | |
| 0.0.41 | 2 / 3 | |
| 0.0.40 | 2 / 3 | |
| 0.0.39 | 2 / 3 | |
| 0.0.38 | 2 / 3 | |
| 0.0.37 | 2 / 3 | |
| 0.0.36 | 2 / 3 | |
| 0.0.35 | 2 / 3 | |
| 0.0.34 | 2 / 3 | |
| 0.0.33 | 2 / 3 | |
| 0.0.32 | 2 / 3 | |
| 0.0.31 | 2 / 3 | |
| 0.0.30 | 2 / 3 | |
| 0.0.29 | 2 / 3 | |
| 0.0.28 | 2 / 3 | |
| 0.0.27 | 2 / 3 | |
| 0.0.26 | 2 / 3 | |
| 0.0.25 | 2 / 3 | |
| 0.0.24 | 2 / 3 |
v0.0.72
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.68
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.62
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.56
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.