@doikayt/typescript-build-config@0.1.32
Shared build configuration for TypeScript projects — ESLint, Prettier, tsconfig, and Playwright presets
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle behavior is real and unprompted, but the inspected source is transparent, package-aligned release tooling without a concrete theft, remote-code, or destructive chain. Warn rather than block.
Decision evidence
public snapshot- Install-time postinstall mutates the consuming project, including GitHub workflow and release-pipeline files.
- Seeded release workflow grants contents/id-token write and uses an NPM secret to publish.
- No credential harvesting, external exfiltration, remote payload loading, eval, or obfuscated source found.
- Playwright browser installation is an explicit executable bin guarded against import-time execution.
- Project config files are skipped when already present; pipeline files are not overwritten when different.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time postinstall mutates the consuming project, including GitHub workflow and release-pipeline files.
package.jsonView on unpkg · L26Findings
Affected versions and remediation
This report applies to @doikayt/typescript-build-config@0.1.32.
See all versions of @doikayt/typescript-build-config for other recorded verdicts.
- Review the evidence and your use of @doikayt/typescript-build-config@0.1.32 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.