@agentuity/core
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') used explicitly to avoid bundler static analysis — documented pattern, not malicious. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @agentuity/core is not a typosquat of cors; different namespace and purpose. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): /etc/passwd reference is inside a JSDoc comment illustrating invalid input examples, not executable code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires a resolved package.json URL for version detection; not arbitrary module loading. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes workbench config passed by the platform; not obfuscated payload execution. | ai |
Versions (showing 100 of 208)
| Version | Deps | Published |
|---|---|---|
| 0.1.38 | 1 / 5 | |
| 0.1.37 | 1 / 5 | |
| 0.1.36 | 1 / 5 | |
| 0.1.35 | 1 / 5 | |
| 0.1.34 | 1 / 5 | |
| 0.1.33 | 1 / 5 | |
| 0.1.32 | 1 / 5 | |
| 0.1.31 | 1 / 5 | |
| 0.1.30 | 1 / 5 | |
| 0.1.29 | 1 / 5 | |
| 0.1.28 | 1 / 5 | |
| 0.1.27 | 1 / 5 | |
| 0.1.26 | 1 / 5 | |
| 0.1.25 | 1 / 5 | |
| 0.1.24 | 1 / 5 | |
| 0.1.23 | 1 / 5 | |
| 0.1.22 | 1 / 5 | |
| 0.1.21 | 1 / 5 | |
| 0.1.20 | 1 / 5 | |
| 0.1.19 | 1 / 5 | |
| 0.1.18 | 1 / 5 | |
| 0.1.17 | 1 / 5 | |
| 0.1.16 | 1 / 5 | |
| 0.1.15 | 1 / 5 | |
| 0.1.14 | 1 / 5 | |
| 0.1.13 | 1 / 5 | |
| 0.1.12 | 1 / 5 | |
| 0.1.11 | 1 / 5 | |
| 0.1.10 | 1 / 5 | |
| 0.1.9 | 1 / 5 | |
| 0.1.8 | 1 / 5 | |
| 0.1.7 | 1 / 5 | |
| 0.1.6 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 1 / 4 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.112 | 1 / 4 | |
| 0.0.111 | 1 / 4 | |
| 0.0.110 | 1 / 4 | |
| 0.0.109 | 1 / 4 | |
| 0.0.108 | 1 / 4 | |
| 0.0.107 | 1 / 4 | |
| 0.0.106 | 1 / 4 | |
| 0.0.105 | 1 / 4 | |
| 0.0.104 | 1 / 4 | |
| 0.0.103 | 1 / 4 | |
| 0.0.102 | 1 / 4 | |
| 0.0.101 | 1 / 4 | |
| 0.0.100 | 1 / 4 | |
| 0.0.99 | 1 / 4 | |
| 0.0.98 | 1 / 4 | |
| 0.0.97 | 1 / 4 | |
| 0.0.96 | 1 / 4 | |
| 0.0.95 | 1 / 4 | |
| 0.0.94 | 1 / 4 | |
| 0.0.93 | 1 / 4 | |
| 0.0.92 | 1 / 4 | |
| 0.0.91 | 1 / 4 | |
| 0.0.90 | 1 / 4 | |
| 0.0.89 | 1 / 4 | |
| 0.0.88 | 1 / 4 | |
| 0.0.87 | 1 / 4 | |
| 0.0.86 | 1 / 4 | |
| 0.0.85 | 1 / 4 | |
| 0.0.84 | 1 / 4 | |
| 0.0.80 | 1 / 4 | |
| 0.0.79 | 1 / 4 | |
| 0.0.78 | 1 / 4 | |
| 0.0.77 | 1 / 4 | |
| 0.0.76 | 1 / 4 | |
| 0.0.75 | 1 / 4 | |
| 0.0.74 | 1 / 4 | |
| 0.0.73 | 1 / 4 | |
| 0.0.72 | 1 / 4 | |
| 0.0.71 | 1 / 4 | |
| 0.0.70 | 1 / 4 | |
| 0.0.69 | 1 / 3 | |
| 0.0.68 | 1 / 3 | |
| 0.0.67 | 1 / 3 | |
| 0.0.66 | 1 / 3 | |
| 0.0.65 | 1 / 3 | |
| 0.0.64 | 1 / 3 | |
| 0.0.63 | 1 / 3 | |
| 0.0.62 | 1 / 3 | |
| 0.0.61 | 1 / 3 | |
| 0.0.60 | 1 / 3 | |
| 0.0.59 | 1 / 3 | |
| 0.0.58 | 1 / 3 | |
| 0.0.57 | 1 / 3 | |
| 0.0.56 | 1 / 3 | |
| 0.0.55 | 1 / 3 | |
| 0.0.54 | 1 / 3 | |
| 0.0.53 | 1 / 3 | |
| 0.0.52 | 1 / 3 | |
| 0.0.51 | 1 / 3 | |
| 0.0.50 | 1 / 3 | |
| 0.0.49 | 1 / 1 |
v0.1.38
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.24
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.111
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.109
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.108
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.107
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.106
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.105
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.103
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.101
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.100
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.97
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.96
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.95
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.94
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.93
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.91
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.90
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.86
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.84
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.76
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.73
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.71
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.69
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.66
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.58
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.57
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.55
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.54
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.52
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.