@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, 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 |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Code refactored into same-org @agentuity/* scoped deps; benign monorepo split. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are official same-org monorepo siblings, not axios-style typosquat risk. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; benign for this actively-maintained package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata-only signals; package is established with real downloads and usage. | ai | |
| phantom-deps | phantom-dep:@agentuity/keyvalue | AI (phantom-deps): Same org scope, likely re-exported indirectly. | ai | |
| dependencies | unvetted-dep:@agentuity/api | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| 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:base64-decode | AI (semgrep): Decodes workbench config passed by the platform; not obfuscated payload execution. | 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 |
Versions (showing 51 of 227)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 5 / 9 | |
| 3.1.5 | 5 / 9 | |
| 3.1.4 | 5 / 9 | |
| 3.1.1 | 5 / 9 | |
| 3.1.0 | 5 / 9 | |
| 3.0.12 | 1 / 4 | |
| 3.0.11 | 1 / 4 | |
| 3.0.10 | 1 / 4 | |
| 3.0.9 | 1 / 4 | |
| 3.0.8 | 1 / 4 | |
| 3.0.7 | 1 / 4 | |
| 3.0.6 | 1 / 4 | |
| 3.0.5 | 1 / 4 | |
| 3.0.4 | 1 / 4 | |
| 3.0.3 | 1 / 4 | |
| 3.0.2 | 1 / 4 | |
| 3.0.1 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.0.30 | 1 / 5 | |
| 2.0.29 | 1 / 5 | |
| 2.0.28 | 1 / 5 | |
| 2.0.27 | 1 / 5 | |
| 2.0.26 | 1 / 5 | |
| 2.0.25 | 1 / 5 | |
| 2.0.24 | 1 / 5 | |
| 2.0.23 | 1 / 5 | |
| 2.0.22 | 1 / 5 | |
| 2.0.21 | 1 / 5 | |
| 2.0.20 | 1 / 5 | |
| 2.0.19 | 1 / 5 | |
| 2.0.18 | 1 / 5 | |
| 2.0.17 | 1 / 5 | |
| 2.0.16 | 1 / 5 | |
| 2.0.15 | 1 / 5 | |
| 2.0.14 | 1 / 5 | |
| 2.0.13 | 1 / 5 | |
| 2.0.12 | 1 / 5 | |
| 2.0.11 | 1 / 5 | |
| 2.0.10 | 1 / 5 | |
| 2.0.9 | 1 / 5 | |
| 2.0.8 | 1 / 5 | |
| 2.0.7 | 1 / 5 | |
| 2.0.6 | 1 / 5 | |
| 2.0.5 | 1 / 5 | |
| 2.0.4 | 1 / 5 | |
| 2.0.3 | 1 / 5 | |
| 2.0.2 | 1 / 5 | |
| 2.0.1 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.0.64 | 1 / 5 | |
| 1.0.63 | 1 / 5 |
v3.1.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jhaynie.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
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: huijiro.
Package 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-06-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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.