@proofkit/typegen
`@proofkit/typegen` is a tool for generating TypeScript types from FileMaker database schemas, making it easier to work with FileMaker data in modern TypeScript projects.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/web/assets/index-DI-YMSzp.js | AI (source-diff): Vite-bundled React web UI; minified output is expected for this package's built-in UI server. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 is a localhost default for the local MCP/FileMaker server connection. | ai | |
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. | ai | |
| dependencies | unvetted-dep:@tanstack/vite-config | AI (dependencies): @tanstack/vite-config is a legitimate TanStack build tooling package; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package in the @proofkit scope; empty description is cosmetic, not a risk signal. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): vite is a declared runtime dep used in build config, not directly imported in source — stable false positive for this build tool. | ai | |
| phantom-deps | phantom-dep:@tanstack/vite-config | AI (phantom-deps): Used in vite build config files, not directly imported in source — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a declared dep used via @commander-js/extra-typings wrapper; phantom detection is a stable false positive here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 22 / 9 | |
| 1.1.2 | 22 / 9 | |
| 1.0.10 | 15 / 6 | |
| 1.0.9 | 15 / 6 | |
| 1.0.8 | 14 / 4 | |
| 1.0.7 | 14 / 4 | |
| 1.0.6 | 14 / 4 | |
| 1.0.5 | 14 / 4 | |
| 1.0.4 | 14 / 4 | |
| 1.0.3 | 14 / 4 | |
| 1.0.2 | 13 / 5 | |
| 1.0.0 | 13 / 4 |
v1.1.3
3 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
3 findingsThis version was published by a different npm account than previous versions on 2026-05-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.