@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 6 of 208)
| Version | Deps | Published |
|---|---|---|
| 0.0.48 | 1 / 1 | |
| 0.0.47 | 1 / 1 | |
| 0.0.46 | 1 / 1 | |
| 0.0.45 | 1 / 1 | |
| 0.0.44 | 1 / 1 | |
| 0.0.43 | 0 / 1 |
v0.0.48
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.47
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.46
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.45
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.44
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.43
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.