@electric-sql/pglite-vue
Vue hooks for using PGlite
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): electric-sql migrated to GitHub Actions CI/CD publishing; SLSA attestation confirms legitimate automated pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org-level CI migration; SLSA provenance confirms legitimate publish source. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 1 / 14 | |
| 0.4.2 | 1 / 14 | |
| 0.4.1 | 1 / 14 | |
| 0.4.0 | 1 / 14 | |
| 0.3.6 | 1 / 13 | |
| 0.3.5 | 1 / 13 | |
| 0.3.4 | 1 / 13 | |
| 0.3.3 | 1 / 13 | |
| 0.3.2 | 1 / 13 | |
| 0.3.1 | 1 / 13 | |
| 0.3.0 | 1 / 13 | |
| 0.2.34 | 1 / 13 | |
| 0.2.33 | 1 / 13 | |
| 0.2.32 | 1 / 13 | |
| 0.2.31 | 1 / 13 | |
| 0.2.30 | 1 / 13 | |
| 0.2.29 | 1 / 13 | |
| 0.2.28 | 1 / 13 | |
| 0.2.27 | 1 / 13 | |
| 0.2.26 | 1 / 13 | |
| 0.2.25 | 1 / 13 | |
| 0.2.24 | 1 / 13 | |
| 0.2.23 | 1 / 13 | |
| 0.2.22 | 1 / 13 | |
| 0.2.21 | 1 / 12 | |
| 0.2.20 | 1 / 12 | |
| 0.2.19 | 1 / 12 | |
| 0.2.18 | 1 / 12 | |
| 0.2.17 | 1 / 12 | |
| 0.2.16 | 1 / 12 | |
| 0.2.15 | 1 / 12 | |
| 0.2.14 | 1 / 12 | |
| 0.2.13 | 1 / 12 | |
| 0.2.12 | 1 / 12 | |
| 0.2.11 | 1 / 12 | |
| 0.2.10 | 1 / 12 | |
| 0.2.9 | 1 / 12 | |
| 0.2.8 | 1 / 12 | |
| 0.2.7 | 1 / 12 | |
| 0.2.6 | 1 / 12 | |
| 0.2.5 | 1 / 12 | |
| 0.2.4 | 1 / 12 | |
| 0.2.3 | 1 / 12 | |
| 0.2.2 | 1 / 12 | |
| 0.2.1 | 1 / 12 | |
| 0.2.0 | 1 / 12 |
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.