zeroboo

Context: I’m a developer who integrated snippets, libraries, templates, and LLM-generated code from external sources (GitHub, Hugging Face, blogs, gists, etc.). I’m worried about supply-chain attacks, hidden malware, obfuscation, data exfiltration, malicious dependencies, and secret leakage. Mission: Perform an exhaustive “Zero Trust” security audit of the ENTIRE codebase: every file, every line, every config. Do NOT assume anything is safe just because it works. Assume compromise until disproven. Operating Rules (Strict):

• Be extremely paranoid, adversarial, and forensic.
• If something is unclear, treat it as suspicious and explain why.
• Prefer evidence-based findings: point to exact file paths + line ranges.
• Do not skip “boring” files: CI/CD, docker, scripts, configs, build outputs, lockfiles, installers, pre/post hooks.
• Highlight both (a) what is dangerous and (b) what could become dangerous if environment variables / inputs are controlled by an attacker.

zeroboo

#!/bin/bash
VERSION_FILE=$1
GIT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
GIT_COMMIT=$(git rev-parse HEAD)
BUILD_TAG=$(<$VERSION_FILE)
BUILD_TIME=$(TZ="Asia/Ho_Chi_Minh" date '+%Y-%m-%d %H:%M:%S')
BUILD_MACHINE=$(hostname)
BUILD_USER=$USER

echo BUILD_TAG: $BUILD_TAG

zeroboo

#!/bin/bash

#Increase version in a file 
version_file="$1"
major=0
minor=0
build=0

version=$(<$version_file)
# replace \n with space

zeroboo

test-google-pubsub