@polpo-ai/drizzle
Drizzle ORM store implementations for the Polpo AI agent orchestration platform (PostgreSQL + SQLite)
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Young monorepo package; lack of provenance is common and no other risk signals present. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 4 / 5 | |
| 0.7.18 | 4 / 5 | |
| 0.7.17 | 4 / 5 | |
| 0.7.16 | 4 / 5 | |
| 0.7.14 | 4 / 5 | |
| 0.7.13 | 4 / 5 | |
| 0.7.12 | 4 / 5 | |
| 0.7.11 | 4 / 5 | |
| 0.7.10 | 4 / 5 | |
| 0.7.9 | 4 / 5 | |
| 0.7.8 | 4 / 5 | |
| 0.7.7 | 4 / 5 | |
| 0.7.6 | 4 / 5 | |
| 0.7.5 | 4 / 5 | |
| 0.7.4 | 4 / 5 | |
| 0.7.3 | 4 / 5 | |
| 0.7.2 | 4 / 5 | |
| 0.7.1 | 4 / 5 | |
| 0.7.0 | 4 / 5 | |
| 0.6.32 | 4 / 5 | |
| 0.6.31 | 4 / 5 | |
| 0.6.30 | 4 / 5 | |
| 0.6.29 | 4 / 5 | |
| 0.6.28 | 4 / 5 | |
| 0.6.27 | 4 / 5 | |
| 0.6.26 | 4 / 5 | |
| 0.6.25 | 4 / 5 | |
| 0.6.24 | 4 / 5 | |
| 0.6.23 | 4 / 5 | |
| 0.6.22 | 4 / 5 | |
| 0.6.21 | 4 / 5 | |
| 0.6.20 | 4 / 5 | |
| 0.6.19 | 4 / 5 | |
| 0.6.18 | 4 / 5 | |
| 0.6.15 | 4 / 5 | |
| 0.6.14 | 4 / 5 | |
| 0.6.13 | 4 / 5 | |
| 0.6.12 | 4 / 5 | |
| 0.6.11 | 4 / 5 | |
| 0.6.10 | 4 / 5 | |
| 0.6.9 | 4 / 5 | |
| 0.6.7 | 4 / 5 | |
| 0.6.6 | 4 / 5 | |
| 0.6.5 | 4 / 5 | |
| 0.6.4 | 4 / 5 | |
| 0.6.3 | 4 / 5 | |
| 0.6.2 | 4 / 5 | |
| 0.6.1 | 4 / 5 | |
| 0.6.0 | 4 / 5 | |
| 0.5.25 | 4 / 5 | |
| 0.5.24 | 4 / 5 | |
| 0.5.23 | 4 / 5 | |
| 0.5.21 | 4 / 5 | |
| 0.5.20 | 4 / 5 | |
| 0.5.18 | 4 / 5 | |
| 0.5.17 | 4 / 5 | |
| 0.5.16 | 4 / 5 | |
| 0.5.14 | 4 / 5 | |
| 0.5.13 | 4 / 5 | |
| 0.5.12 | 4 / 5 | |
| 0.5.9 | 4 / 5 | |
| 0.5.8 | 4 / 5 | |
| 0.5.7 | 4 / 5 | |
| 0.5.6 | 4 / 5 | |
| 0.5.5 | 4 / 5 | |
| 0.5.4 | 4 / 5 | |
| 0.5.3 | 4 / 5 | |
| 0.5.2 | 4 / 5 | |
| 0.5.1 | 4 / 5 | |
| 0.5.0 | 4 / 5 | |
| 0.4.10 | 4 / 5 | |
| 0.4.9 | 4 / 5 | |
| 0.4.8 | 4 / 5 | |
| 0.4.7 | 4 / 5 | |
| 0.4.6 | 4 / 5 | |
| 0.4.5 | 4 / 5 | |
| 0.4.4 | 4 / 5 | |
| 0.4.3 | 4 / 5 | |
| 0.4.2 | 4 / 5 | |
| 0.4.1 | 4 / 5 | |
| 0.4.0 | 4 / 5 | |
| 0.2.13 | 4 / 5 | |
| 0.2.12 | 4 / 5 | |
| 0.2.11 | 4 / 5 | |
| 0.2.10 | 4 / 5 | |
| 0.2.9 | 4 / 5 | |
| 0.2.8 | 4 / 5 | |
| 0.2.7 | 4 / 5 | |
| 0.2.6 | 4 / 5 | |
| 0.2.5 | 4 / 5 | |
| 0.2.4 | 4 / 5 | |
| 0.2.3 | 4 / 5 | |
| 0.2.2 | 4 / 5 | |
| 0.2.1 | 4 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 |
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.