@pgsql/transform
AST-based SQL transformation, qualification, classification and closure analysis for PostgreSQL
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:18/enums.d.ts | AI (source-diff): Autogenerated .d.ts with long union types, not obfuscated executable code. | ai | |
| dependencies | unvetted-dep:plpgsql-parser | AI (dependencies): Sibling package in the same pgsql-parser monorepo family, not third-party. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Refactor splitting functionality into sibling packages, no malicious payload evidence. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop corresponds to code moved into new @pgsql/* deps, not stubbing. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 18.3.1 | 3 / 1 | |
| 18.3.0 | 3 / 1 | |
| 18.1.1 | 0 / 6 | |
| 18.1.0 | 0 / 6 | |
| 18.0.0 | 0 / 6 | |
| 17.9.19 | 0 / 4 | |
| 17.9.18 | 0 / 4 | |
| 17.9.17 | 0 / 4 | |
| 17.9.16 | 0 / 4 | |
| 17.9.15 | 0 / 4 | |
| 17.9.14 | 0 / 4 | |
| 17.9.13 | 0 / 4 |
v18.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (rollup) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (rollup) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (rollup) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.