@agentuity/server
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is stable metadata issue, not a security signal. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep releases publish rapidly across sibling packages; benign. | ai | |
| dependencies | unvetted-dep:@agentuity/api | AI (dependencies): First-party sibling package in the same monorepo/version lockstep. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Major version refactor splitting monolith into sibling @agentuity/* packages; size increase is structural, not injected payload. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 342 new files reflect monorepo restructure at v3; stable pattern for this package going forward. | ai | |
| provenance | no-provenance | AI (provenance): Established Agentuity org package; lack of Sigstore attestation is a process gap, not a security risk for this publisher. | ai | |
| provenance | missing-githead | AI (provenance): Agentuity monorepo; publisher has 1549 approved packages; missing gitHead is a CI process change, not a supply-chain indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @agentuity/[email protected] — same org/version family, not a suspicious third-party package. | ai | |
| provenance | publisher-changed | AI (provenance): p0tofpie is a high-volume trusted publisher (1041 approved); transition appears to be an org-internal maintainer change. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Fires on a JSDoc comment string showing invalid input examples, not actual /etc/passwd access. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK component; sparse metadata is consistent across all 254 versions of this package. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @agentuity package; Levenshtein match to 'semver' is a false positive with no brand impersonation intent. | ai |
Versions (showing 51 of 227)
| Version | Deps | Published |
|---|---|---|
| 3.1.9 | 9 / 5 | |
| 3.1.5 | 9 / 5 | |
| 3.1.2 | 9 / 5 | |
| 3.1.1 | 9 / 5 | |
| 3.1.0 | 9 / 5 | |
| 3.0.12 | 3 / 5 | |
| 3.0.11 | 3 / 5 | |
| 3.0.10 | 3 / 5 | |
| 3.0.9 | 3 / 5 | |
| 3.0.8 | 3 / 5 | |
| 3.0.7 | 3 / 5 | |
| 3.0.6 | 3 / 5 | |
| 3.0.5 | 3 / 5 | |
| 3.0.4 | 3 / 5 | |
| 3.0.3 | 3 / 5 | |
| 3.0.2 | 3 / 5 | |
| 3.0.1 | 3 / 5 | |
| 3.0.0 | 3 / 5 | |
| 2.0.30 | 3 / 5 | |
| 2.0.29 | 3 / 5 | |
| 2.0.28 | 3 / 5 | |
| 2.0.27 | 3 / 5 | |
| 2.0.26 | 3 / 5 | |
| 2.0.25 | 3 / 5 | |
| 2.0.24 | 3 / 5 | |
| 2.0.23 | 3 / 5 | |
| 2.0.22 | 3 / 5 | |
| 2.0.21 | 3 / 5 | |
| 2.0.20 | 3 / 5 | |
| 2.0.19 | 3 / 5 | |
| 2.0.18 | 3 / 5 | |
| 2.0.17 | 3 / 5 | |
| 2.0.16 | 3 / 5 | |
| 2.0.15 | 3 / 5 | |
| 2.0.14 | 3 / 5 | |
| 2.0.13 | 3 / 5 | |
| 2.0.12 | 3 / 5 | |
| 2.0.11 | 3 / 5 | |
| 2.0.10 | 3 / 5 | |
| 2.0.9 | 3 / 5 | |
| 2.0.8 | 3 / 5 | |
| 2.0.7 | 3 / 5 | |
| 2.0.6 | 3 / 5 | |
| 2.0.5 | 3 / 5 | |
| 2.0.4 | 3 / 5 | |
| 2.0.3 | 3 / 5 | |
| 2.0.2 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.0.64 | 3 / 5 | |
| 1.0.63 | 3 / 5 |
v3.1.9
2 findings[Accepted risk] 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 (p0tofpie) on 2026-07-08, 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.5
2 findings[Accepted risk] 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 (p0tofpie) 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.