@byline/db-postgres
Byline CMS db postgres package
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod used in config/type declarations in a TS monorepo; not a direct import but legitimately declared. | ai | |
| phantom-deps | phantom-dep:npm-run-all | AI (phantom-deps): npm-run-all is a build/dev tooling dep referenced in scripts, not imported in source. | ai | |
| phantom-deps | phantom-dep:@byline/auth | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 8 / 11 | |
| 3.2.1 | 8 / 11 | |
| 3.2.0 | 8 / 11 | |
| 3.1.1 | 8 / 11 | |
| 3.1.0 | 8 / 11 | |
| 3.0.2 | 8 / 11 | |
| 3.0.1 | 8 / 11 | |
| 3.0.0 | 8 / 11 | |
| 2.7.0 | 8 / 11 | |
| 2.6.1 | 8 / 11 | |
| 2.6.0 | 8 / 11 | |
| 2.5.2 | 8 / 11 | |
| 2.5.1 | 8 / 11 | |
| 2.5.0 | 8 / 11 | |
| 2.4.4 | 8 / 11 | |
| 2.4.3 | 8 / 11 | |
| 2.4.2 | 8 / 11 | |
| 2.4.1 | 8 / 11 | |
| 2.4.0 | 8 / 11 | |
| 2.3.3 | 8 / 11 | |
| 2.3.2 | 8 / 11 | |
| 2.3.1 | 8 / 11 | |
| 2.3.0 | 8 / 11 | |
| 2.2.10 | 8 / 11 | |
| 2.2.9 | 8 / 11 | |
| 2.2.8 | 8 / 11 | |
| 2.2.7 | 8 / 11 | |
| 2.2.6 | 8 / 11 | |
| 2.2.5 | 8 / 11 | |
| 2.2.4 | 8 / 11 | |
| 2.2.3 | 8 / 11 | |
| 2.2.2 | 8 / 11 | |
| 2.2.1 | 8 / 11 | |
| 2.2.0 | 8 / 11 | |
| 2.1.3 | 8 / 11 | |
| 2.1.2 | 8 / 11 | |
| 2.1.1 | 8 / 11 | |
| 2.1.0 | 8 / 11 | |
| 1.12.2 | 8 / 11 | |
| 1.12.1 | 8 / 9 | |
| 1.12.0 | 8 / 9 | |
| 1.11.2 | 8 / 9 | |
| 1.11.1 | 8 / 9 | |
| 1.11.0 | 8 / 9 | |
| 1.10.3 | 8 / 9 | |
| 1.10.2 | 8 / 9 | |
| 1.10.1 | 8 / 9 | |
| 1.10.0 | 8 / 9 | |
| 1.9.1 | 8 / 9 | |
| 1.9.0 | 8 / 9 | |
| 1.8.2 | 8 / 9 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.