@agentuity/runtime
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:@types/ws | AI (phantom-deps): @types packages are type-only and loaded by convention, not direct import. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 is a localhost server binding, not an exfiltration endpoint. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used for HMAC signature comparison; standard crypto pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a newly added runtime dep; phantom-dep heuristic likely fires before import wiring is complete. | ai | |
| phantom-deps | phantom-dep:@agentuity/schema | AI (phantom-deps): Same-org schema package; likely used via type imports or re-exports not caught by the heuristic. | ai | |
| phantom-deps | phantom-dep:@types/mailparser | AI (phantom-deps): @types packages are type-only and won't appear as direct imports. | ai |
Versions (showing 51 of 129)
| Version | Deps | Published |
|---|---|---|
| 3.0.5 | 0 / 1 | |
| 3.0.4 | 0 / 1 | |
| 3.0.3 | 0 / 1 | |
| 3.0.2 | 0 / 1 | |
| 3.0.1 | 0 / 1 | |
| 3.0.0 | 0 / 1 | |
| 2.0.22 | 21 / 11 | |
| 2.0.21 | 21 / 11 | |
| 2.0.20 | 21 / 11 | |
| 2.0.19 | 21 / 11 | |
| 2.0.18 | 21 / 11 | |
| 2.0.17 | 21 / 11 | |
| 2.0.16 | 21 / 11 | |
| 2.0.15 | 21 / 11 | |
| 2.0.14 | 21 / 11 | |
| 2.0.13 | 21 / 11 | |
| 2.0.12 | 21 / 11 | |
| 2.0.11 | 21 / 11 | |
| 2.0.10 | 21 / 11 | |
| 2.0.9 | 21 / 11 | |
| 2.0.8 | 21 / 11 | |
| 2.0.7 | 21 / 11 | |
| 2.0.6 | 21 / 11 | |
| 2.0.5 | 21 / 11 | |
| 2.0.4 | 21 / 11 | |
| 2.0.3 | 21 / 11 | |
| 2.0.2 | 21 / 11 | |
| 2.0.1 | 21 / 11 | |
| 2.0.0 | 22 / 11 | |
| 1.0.64 | 22 / 11 | |
| 1.0.63 | 22 / 11 | |
| 1.0.62 | 22 / 11 | |
| 1.0.61 | 22 / 11 | |
| 1.0.60 | 22 / 11 | |
| 1.0.59 | 22 / 11 | |
| 1.0.58 | 22 / 11 | |
| 1.0.57 | 22 / 11 | |
| 1.0.56 | 22 / 11 | |
| 1.0.55 | 22 / 11 | |
| 1.0.54 | 22 / 11 | |
| 1.0.53 | 22 / 11 | |
| 1.0.52 | 22 / 11 | |
| 1.0.51 | 22 / 11 | |
| 1.0.50 | 22 / 11 | |
| 1.0.49 | 22 / 11 | |
| 1.0.48 | 22 / 11 | |
| 1.0.47 | 22 / 11 | |
| 1.0.46 | 22 / 11 | |
| 1.0.45 | 22 / 11 | |
| 1.0.44 | 22 / 11 | |
| 1.0.43 | 22 / 11 |
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (huijiro) than the most recent previously approved version (p0tofpie) on 2026-05-29, but huijiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (huijiro) than the most recent previously approved version (jhaynie) on 2026-05-25, but huijiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.22
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: p0tofpie.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (p0tofpie) than the most recent previously approved version (huijiro) on 2026-05-27, but p0tofpie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
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.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.