@agentuity/db
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@agentuity/api | AI (dependencies): First-party @agentuity/* monorepo package pinned at matching version; not a third-party unvetted dep. | ai | |
| provenance | missing-githead | AI (provenance): Publisher has strong track record; likely a CI/publish environment change within the same org, not a supply chain indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package; no description/repo/keywords is expected for private monorepo-style packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is @agentuity/server from the same org scope and pinned to the same version — consistent monorepo release pattern. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped org package @agentuity/db; not a typosquat of pg. | ai | |
| phantom-deps | phantom-dep:@agentuity/server | AI (phantom-deps): Same-org dependency; likely used transitively or re-exported rather than directly imported. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped org package @agentuity/db; not a typosquat of qs. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 3.1.5 | 6 / 3 | |
| 3.1.1 | 6 / 3 | |
| 3.0.12 | 2 / 3 | |
| 3.0.11 | 2 / 3 | |
| 3.0.10 | 2 / 3 | |
| 3.0.9 | 2 / 3 | |
| 3.0.8 | 2 / 3 | |
| 3.0.7 | 2 / 3 | |
| 3.0.6 | 2 / 3 | |
| 3.0.5 | 2 / 3 | |
| 3.0.4 | 2 / 3 | |
| 3.0.3 | 2 / 3 | |
| 3.0.2 | 2 / 3 | |
| 3.0.1 | 2 / 3 | |
| 3.0.0 | 2 / 3 | |
| 2.0.30 | 3 / 4 | |
| 2.0.29 | 3 / 4 | |
| 2.0.28 | 3 / 4 | |
| 2.0.27 | 3 / 4 | |
| 2.0.26 | 3 / 4 | |
| 2.0.25 | 3 / 4 | |
| 2.0.24 | 3 / 4 | |
| 2.0.23 | 3 / 4 | |
| 2.0.22 | 3 / 4 | |
| 2.0.21 | 3 / 4 | |
| 2.0.20 | 3 / 4 | |
| 2.0.19 | 3 / 4 | |
| 2.0.18 | 3 / 4 | |
| 2.0.17 | 3 / 4 | |
| 2.0.16 | 3 / 4 | |
| 2.0.15 | 3 / 4 | |
| 2.0.14 | 3 / 4 | |
| 2.0.13 | 3 / 4 | |
| 2.0.12 | 3 / 4 | |
| 2.0.11 | 3 / 4 | |
| 2.0.10 | 3 / 4 | |
| 2.0.9 | 3 / 4 | |
| 2.0.8 | 3 / 4 | |
| 2.0.7 | 3 / 4 | |
| 2.0.6 | 3 / 4 | |
| 2.0.5 | 3 / 4 | |
| 2.0.4 | 3 / 4 | |
| 2.0.3 | 3 / 4 | |
| 2.0.2 | 3 / 4 | |
| 2.0.1 | 3 / 4 | |
| 2.0.0 | 3 / 4 | |
| 1.0.64 | 3 / 4 | |
| 1.0.63 | 3 / 4 | |
| 1.0.62 | 3 / 4 | |
| 1.0.61 | 3 / 4 | |
| 1.0.60 | 3 / 4 |
v3.1.5
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-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.