Below you will find pages that utilize the taxonomy term “Theinfosecguy”
August 26, 2026
SlopLock
Version updated for https://github.com/theinfosecguy/sloplock to version v2.2.0.
This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24.
Go to the GitHub Marketplace to find the latest changes.
Action Summary SlopLock is an automated security tool that helps prevent the installation of AI-generated or malicious dependencies by checking their existence, age, and trustworthiness across multiple public registries. It solves the problem of identifying and blocking new, potentially harmful packages before they can be installed on developer machines or merged into pull requests. The action checks each dependency name for existence and age, providing a summary report with annotations and job summaries for easy tracking and management.
August 26, 2026
SlopLock
Version updated for https://github.com/theinfosecguy/sloplock to version v2.1.0.
This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The SlopLock GitHub Action automates the process of identifying and blocking AI-hallucinated, nonexistent, and too-new dependencies before they are installed or merged into a project. It helps prevent security vulnerabilities by ensuring that only verified package names are used. The action scans dependencies across eight public registries and provides detailed reports to help developers and maintainers validate package names.
August 25, 2026
SlopLock
Version updated for https://github.com/theinfosecguy/sloplock to version v2.0.0.
This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24.
Go to the GitHub Marketplace to find the latest changes.
Action Summary SlopLock is a GitHub Action that checks package names before they are installed or merged, ensuring the packages exist and are not too new. It identifies AI-hallucinated, nonexistent, and too-new dependencies by asking eight public registries if they exist and have sufficient history to trust them. The tool posts comments on pull requests with details about the findings and helps maintain a secure dependency ecosystem.