@axiom-lattice/pg-stores
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all 55 versions; maintainer hasn't enabled Sigstore provenance but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:@axiom-lattice/core | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported, stable FP for this package. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 1.0.91 | 7 / 9 | |
| 1.0.90 | 7 / 9 | |
| 1.0.89 | 7 / 6 | |
| 1.0.88 | 7 / 6 | |
| 1.0.87 | 7 / 6 | |
| 1.0.86 | 7 / 6 | |
| 1.0.85 | 5 / 6 | |
| 1.0.84 | 5 / 6 | |
| 1.0.83 | 5 / 6 | |
| 1.0.82 | 5 / 6 | |
| 1.0.81 | 5 / 6 | |
| 1.0.80 | 5 / 6 | |
| 1.0.79 | 5 / 6 | |
| 1.0.78 | 5 / 6 | |
| 1.0.77 | 5 / 6 | |
| 1.0.76 | 5 / 6 | |
| 1.0.75 | 5 / 6 | |
| 1.0.74 | 5 / 6 | |
| 1.0.73 | 5 / 6 | |
| 1.0.72 | 5 / 6 | |
| 1.0.71 | 4 / 6 | |
| 1.0.70 | 4 / 6 | |
| 1.0.69 | 4 / 6 | |
| 1.0.68 | 4 / 6 | |
| 1.0.67 | 4 / 6 | |
| 1.0.66 | 4 / 6 | |
| 1.0.65 | 4 / 6 | |
| 1.0.64 | 4 / 6 | |
| 1.0.63 | 4 / 6 | |
| 1.0.62 | 4 / 6 | |
| 1.0.61 | 4 / 6 | |
| 1.0.60 | 4 / 6 | |
| 1.0.59 | 4 / 6 | |
| 1.0.58 | 4 / 6 | |
| 1.0.57 | 4 / 6 | |
| 1.0.56 | 4 / 6 | |
| 1.0.55 | 4 / 6 | |
| 1.0.54 | 4 / 6 | |
| 1.0.53 | 3 / 5 | |
| 1.0.52 | 3 / 5 | |
| 1.0.51 | 3 / 5 | |
| 1.0.50 | 3 / 5 | |
| 1.0.49 | 3 / 5 | |
| 1.0.48 | 3 / 5 | |
| 1.0.47 | 3 / 5 | |
| 1.0.46 | 3 / 5 | |
| 1.0.45 | 3 / 5 | |
| 1.0.44 | 3 / 5 | |
| 1.0.43 | 3 / 5 | |
| 1.0.42 | 3 / 5 | |
| 1.0.41 | 3 / 5 |
v1.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.