@agentuity/drizzle
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Agentuity org package with consistent publish cadence; single missing gitHead not indicative of supply-chain compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): better-auth is an established auth library; addition in a Drizzle integration is contextually appropriate. | ai | |
| provenance | publisher-changed | AI (provenance): p0tofpie is a high-volume trusted publisher (1307 approved) within the same Agentuity org; consistent with an internal account transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): p0tofpie is an established publisher (1046 approved packages) within the @agentuity org; transition appears legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Org-published package; absence of Sigstore provenance is common and no other risk signals present. | ai |
Versions (showing 51 of 128)
| Version | Deps | Published |
|---|---|---|
| 3.1.13 | 3 / 4 | |
| 3.1.12 | 3 / 4 | |
| 3.1.11 | 3 / 4 | |
| 3.1.10 | 3 / 4 | |
| 3.1.9 | 3 / 4 | |
| 3.1.8 | 3 / 4 | |
| 3.1.7 | 3 / 4 | |
| 3.1.6 | 3 / 4 | |
| 3.1.5 | 3 / 4 | |
| 3.1.4 | 3 / 4 | |
| 3.1.3 | 3 / 4 | |
| 3.1.2 | 3 / 4 | |
| 3.1.1 | 3 / 4 | |
| 3.1.0 | 3 / 4 | |
| 3.0.12 | 3 / 4 | |
| 3.0.11 | 3 / 4 | |
| 3.0.10 | 3 / 4 | |
| 3.0.9 | 3 / 4 | |
| 3.0.8 | 3 / 4 | |
| 3.0.7 | 3 / 4 | |
| 3.0.6 | 3 / 4 | |
| 3.0.5 | 3 / 4 | |
| 3.0.4 | 3 / 4 | |
| 3.0.3 | 3 / 4 | |
| 3.0.2 | 3 / 4 | |
| 3.0.1 | 3 / 4 | |
| 3.0.0 | 3 / 4 | |
| 2.0.30 | 4 / 4 | |
| 2.0.29 | 4 / 4 | |
| 2.0.28 | 4 / 4 | |
| 2.0.27 | 4 / 4 | |
| 2.0.26 | 4 / 4 | |
| 2.0.25 | 4 / 4 | |
| 2.0.24 | 4 / 4 | |
| 2.0.23 | 4 / 4 | |
| 2.0.22 | 4 / 4 | |
| 2.0.21 | 4 / 4 | |
| 2.0.20 | 4 / 4 | |
| 2.0.19 | 4 / 4 | |
| 2.0.18 | 4 / 4 | |
| 2.0.17 | 4 / 4 | |
| 2.0.16 | 4 / 4 | |
| 2.0.15 | 4 / 4 | |
| 2.0.14 | 4 / 4 | |
| 2.0.13 | 4 / 4 | |
| 2.0.12 | 4 / 4 | |
| 2.0.11 | 4 / 4 | |
| 2.0.10 | 4 / 4 | |
| 2.0.9 | 4 / 4 | |
| 2.0.8 | 4 / 4 | |
| 2.0.7 | 4 / 4 |
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
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 (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-20, but jhaynie 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.10
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 (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-20, but jhaynie 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.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 (jhaynie) 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.8
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 (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-06, but jhaynie 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.7
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 (jhaynie) on 2026-07-03, 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.6
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 (jhaynie) than the most recent previously approved version (p0tofpie) on 2026-07-02, but jhaynie 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.
v2.0.30
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 (p0tofpie) than the most recent previously approved version (huijiro) on 2026-06-25, but p0tofpie 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.