#software-supply-chain — Public Fediverse posts

Το #OpenSource είναι παντού, αλλά η ψηφιακή μας υποδομή συχνά στηρίζεται σε έναν εξουθενωμένο maintainer. 🐘🛠️

Στο νέο άρθρο, αναλύω το "Trust-State Inversion", το GSD incident και το xz backdoor. Πώς μπορούμε να χτίσουμε μια πραγματική αγορά εμπιστοσύνης στην Ευρώπη με το επερχόμενο Cyber Resilience Act (#CRA);

Η λύση κρύβεται στη σωστή χρηματοδότηση και τα ανοιχτά πρότυπα.

👉 https://eiosifidis.blogspot.com/2026/07/open-source-trust-cra-ai-security.html

#Linux #Cybersecurity #openSUSE #InfoSec #SoftwareSupplyChain #TechSovereignty #Tech

Το #OpenSource είναι παντού, αλλά η ψηφιακή μας υποδομή συχνά στηρίζεται σε έναν εξουθενωμένο maintainer. 🐘🛠️

Στο νέο άρθρο, αναλύω το "Trust-State Inversion", το GSD incident και το xz backdoor. Πώς μπορούμε να χτίσουμε μια πραγματική αγορά εμπιστοσύνης στην Ευρώπη με το επερχόμενο Cyber Resilience Act (#CRA);

Η λύση κρύβεται στη σωστή χρηματοδότηση και τα ανοιχτά πρότυπα.

👉 https://eiosifidis.blogspot.com/2026/07/open-source-trust-cra-ai-security.html

#Linux #Cybersecurity #openSUSE #InfoSec #SoftwareSupplyChain #TechSovereignty #Tech

We have released a new version for the first time in a long while. As well as the usual software updates, it includes our experience with agent-based code generation and securing the software supply chain: https://www.python4data.science/en/26.1.0/
#Python #DataScience #AgenticCoding #Claude #SoftwareEngineering #SoftwareSupplyChain #SupplyChain

We have released a new version for the first time in a long while. As well as the usual software updates, it includes our experience with agent-based code generation and securing the software supply chain: https://www.python4data.science/en/26.1.0/
#Python #DataScience #AgenticCoding #Claude #SoftwareEngineering #SoftwareSupplyChain #SupplyChain

Recent attacks on TanStack, Axios, Nx Console, and DAEMON Tools reveal why code signing and software provenance prove origin, not safety. https://hackernoon.com/your-software-supply-chain-only-proves-where-code-came-from-not-whether-its-safe #softwaresupplychain

Recent attacks on TanStack, Axios, Nx Console, and DAEMON Tools reveal why code signing and software provenance prove origin, not safety. https://hackernoon.com/your-software-supply-chain-only-proves-where-code-came-from-not-whether-its-safe #softwaresupplychain

Three open-source AI agent skill managers have each reached 2,000 GitHub stars in months. Problem: skills are natural-language instructions agents execute with full file and shell access. Only one of the three scans skill files for attacks before use. That's a supply-chain gap worth watching. https://www.implicator.ai/ai-agent-skill-managers-are-a-supply-chain-surface-most-of-them-dont-guard/ #infosec #AI #softwaresupplychain

Three open-source AI agent skill managers have each reached 2,000 GitHub stars in months. Problem: skills are natural-language instructions agents execute with full file and shell access. Only one of the three scans skill files for attacks before use. That's a supply-chain gap worth watching. https://www.implicator.ai/ai-agent-skill-managers-are-a-supply-chain-surface-most-of-them-dont-guard/ #infosec #AI #softwaresupplychain

Microsoft Probes Miasma Campaign as GitHub Repos Remain Offline

Microsoft swiftly took action to safeguard its customers and the broader ecosystem by temporarily removing some GitHub repositories while investigating a software supply chain intrusion. The company has since restored some, but others remain offline as the probe continues.

https://osintsights.com/microsoft-probes-miasma-campaign-as-github-repos-remain-offline?utm_source=mastodon&utm_medium=social

#SoftwareSupplyChain #Github #Microsoft #EmergingThreats #InformationStealer

#RedHat: More than 30 #npm packages under Red Hat's '@redhat-cloud-services' namespace were compromised in a supply-chain attack to steal developer credentials including GitHub secrets, AWS/Azure/GCP credentials, npm & PYPI tokens:
#SoftwareSupplyChain
👇
https://www.bleepingcomputer.com/news/security/red-hat-npm-packages-compromised-to-steal-developer-credentials/

#RedHat: More than 30 #npm packages under Red Hat's '@redhat-cloud-services' namespace were compromised in a supply-chain attack to steal developer credentials including GitHub secrets, AWS/Azure/GCP credentials, npm & PYPI tokens:
#SoftwareSupplyChain
👇
https://www.bleepingcomputer.com/news/security/red-hat-npm-packages-compromised-to-steal-developer-credentials/

The New Digital Battlefield: Why 2026 Demands a Hardened Security Stance

2,251 words, 12 minutes read time.

The digital landscape has fundamentally shifted, and if you are still looking at your network through the lens of yesterday’s defensive strategies, you are already behind. We have entered an era where the perimeter is not just porous; it is effectively non-existent. As we navigate 2026, the rise of agentic artificial intelligence has transformed the threat landscape from a series of isolated incidents into a continuous, automated, and relentless war of attrition. Adversaries are no longer manually probing for weaknesses during business hours; they are deploying autonomous software agents that scout, exploit, and pivot through complex multi-cloud environments without human intervention. This shift marks the end of the era where reactive patch management and static firewall rules could keep an enterprise safe. Analyzing the current trajectory of these automated threats, it is clear that the primary battlefield has moved from the network edge to the identity layer, making every single access request a potential point of compromise that requires immediate, granular verification.

The Weaponization of Intelligence and the Death of Perimeter Defense

The most significant change to the security landscape this year is the democratization of sophisticated offensive tools. Attackers have evolved beyond simple phishing schemes, utilizing generative models to craft hyper-personalized deception campaigns that are virtually indistinguishable from legitimate communications. These are not the poorly translated emails of a decade ago; these are synthesized audio, video, and text-based deepfakes that exploit human psychology by mimicking trusted colleagues or vendors. When I look at the rapid maturation of these technologies, I see a clear pattern of adversaries targeting the human element while simultaneously leveraging machine learning to identify and exploit zero-day vulnerabilities in public-facing applications. The traditional concept of a “trusted network” has been completely eroded by this reality. It is no longer enough to guard the gates; organizations must now assume that their internal environments are already compromised and operate with a mindset of constant, zero-trust verification.

Moving Beyond Prevention Toward Active Operational Resilience

Prevention remains a fundamental goal, but in 2026, it is no longer the sole pillar of a successful security posture. The smartest organizations are now shifting their focus toward operational resilience, which acknowledges the inevitability of a security incident and prioritizes the ability to withstand, contain, and recover from such events in real time. This transition requires a move away from reliance on human analysts to manually triage every alert. We are seeing a necessary pivot toward automated incident response frameworks that can detect anomalies and orchestrate remediation actions at machine speed. By integrating security orchestration, automation, and response tools into a unified platform, security teams are finally beginning to close the gap between detection and mitigation. This level of responsiveness is the only way to counter the speed of agentic AI attacks, as traditional manual processes are simply too slow to keep pace with an adversary that never sleeps and never tires.

The Silent Expansion of the Shadow AI Workforce

One of the most insidious threats currently facing enterprises is the unchecked proliferation of shadow AI agents. In 2026, it is no longer just about employees using unapproved chatbots to summarize meeting notes; we are witnessing the deployment of autonomous agents that have been granted direct, persistent access to critical business data and internal systems. These digital coworkers operate with a level of agency that far outstrips simple automation, performing tasks like financial reporting, supply chain adjustments, and email management without constant human oversight. When an organization fails to maintain a comprehensive inventory of these agents, it effectively creates a shadow workforce that exists entirely outside the purview of traditional identity and access management systems. This identity sprawl introduces a massive, hidden attack surface where a single misconfigured agent—or one compromised through a malicious prompt injection—can initiate a cascade of unauthorized actions across the corporate network. Because these agents are designed to move data and execute processes, they essentially function as authorized insiders with elevated privileges, making the task of distinguishing between legitimate autonomous operations and malicious activity an increasingly complex needle-in-a-haystack problem.

Why Identity Has Replaced the Network as the Primary Battleground

For years, the industry obsessed over the network perimeter, pouring capital into firewalls and intrusion detection systems to keep the bad guys out. That era is definitively over. In the current threat environment, identity is the new perimeter, and it is failing under the weight of AI-powered credential abuse and deepfake deception. Attackers are no longer focused on finding a hole in a firewall; they are finding ways to walk through the front door using stolen or synthesized credentials that appear entirely authentic. When I evaluate the efficacy of modern security controls, it is obvious that static multi-factor authentication is no longer enough to stop an adversary who can perform real-time biometric spoofing or orchestrate a multi-stage social engineering attack that mimics an executive’s voice or likeness during a critical transaction. Every single access request must now be treated as a high-stakes event, validated against real-time behavioral patterns, device health telemetry, and geolocation data. We have moved into a world where trust must be continuously earned through granular verification, and any system that assumes a user or an agent is “trusted” based on a single point of entry is simply begging to be exploited.

The Rising Tide of Supply Chain and API Vulnerabilities

While the focus on agentic AI and identity is necessary, we cannot afford to ignore the systemic rot within our interconnected software ecosystems. Modern applications are built on a sprawling web of third-party APIs, open-source libraries, and cloud-native integrations that create countless back doors into an organization’s most sensitive data. Attackers have realized that they do not need to break through the fortified front door of a target company when they can instead compromise a trusted vendor, a CI/CD workflow, or an OAuth token that grants them indirect, authenticated access. The data from the past year confirms a dramatic increase in the exploitation of public-facing applications, often leveraged through these compromised trust relationships. This means that an organization’s security posture is only as strong as its weakest third-party integration. Moving forward, the only way to mitigate this risk is to treat every API and every software dependency as a potential ingress point, enforcing rigorous oversight and ensuring that security transparency extends far beyond the internal walls of the enterprise.

The Escalation of Data Poisoning and Model Integrity Risks

While much of the industry attention has been captured by the potential for AI-driven external attacks, there is an equally dangerous, albeit quieter, evolution occurring within the integrity of the data that powers these systems. We are currently facing a crisis of confidence regarding the inputs that drive corporate decision-making and autonomous workflows. In 2026, it is not enough to secure the infrastructure; we must now confront the reality of data poisoning, where adversaries inject subtle, malicious anomalies into the datasets used for training or fine-tuning enterprise machine learning models. This is not about a sudden, catastrophic system failure that triggers a loud alarm; it is about the gradual, calculated subversion of business logic. When an attacker successfully manipulates the underlying data, they can induce a model to make flawed recommendations, prioritize fraudulent transactions, or ignore malicious patterns in security logs. This turns a company’s most potent technological asset into a Trojan horse, working silently against the organization’s interests from the inside out. Securing the data pipeline has become a top-tier security imperative, requiring rigorous provenance tracking, continuous auditability of training sets, and the implementation of robust adversarial training techniques designed to identify and reject manipulated inputs before they can degrade the model’s reliability.

Addressing the Looming Talent Gap and Defensive Burnout

The rapid pace of technological change is not only taxing our technical systems; it is pushing human defenders to their absolute breaking point. We are operating in an environment where the volume, variety, and velocity of security alerts have completely outstripped the cognitive capacity of traditional security operations center teams. Expecting human analysts to keep pace with adversaries who are utilizing automated agents to conduct attacks at machine speed is a recipe for failure and inevitable burnout. This is why the integration of advanced analytics and automated triage is no longer just a luxury for the largest organizations; it is a fundamental survival requirement. The goal is to move the human element up the value chain, shifting the focus from mundane, repetitive monitoring tasks toward high-level threat hunting, architecture design, and strategic oversight. By offloading the grunt work of log aggregation, initial correlation, and basic incident containment to intelligent machines, we can preserve the sanity of our teams while simultaneously reducing the dwell time of attackers within our environments. A security strategy that fails to account for the human element of this equation is doomed to fall apart as the attrition rates in cybersecurity continue to climb in response to this relentless, high-pressure digital conflict.

Building a Future-Proof Architecture Based on Radical Transparency

Looking toward the remainder of this year and beyond, the only way for any organization to maintain a viable security stance is to embrace a philosophy of radical transparency and aggressive defensive engineering. We must abandon the secrecy that has historically defined corporate security departments and instead adopt a model of shared intelligence. This means actively participating in industry threat-sharing consortia, automating the ingestion of real-time indicators of compromise, and building systems that are designed to be observable at every layer of the stack. A closed, proprietary system is inherently more fragile in the current climate than an open, well-audited, and resilient architecture. We need to move toward a future where security controls are not just bolted onto existing infrastructure as an afterthought, but are instead natively woven into the software development lifecycle, the CI/CD pipeline, and the very identity frameworks that govern access. The threats we face today are systemic and collaborative; our defenses must be equally coordinated, pervasive, and uncompromising if we are to have any hope of maintaining control over our digital domains.

The Final Synthesis: Adapting to the Persistent Threat Paradigm

As we look toward the horizon, it becomes clear that the distinction between a peaceful digital state and an active security incident has effectively dissolved. We are no longer living in a world of binary outcomes where one is either secure or compromised. Instead, we are navigating a permanent state of high-intensity conflict where persistent, automated threats constantly probe for the slightest deviation in our operational baseline. Success in this environment is not defined by the absence of attacks, but by the ability to maintain the continuity of business operations while under fire. This requires a fundamental departure from the legacy mindset of static defenses and annual compliance audits. It demands a posture that is defined by agility, continuous monitoring, and the willingness to radically restructure how we manage identity, data, and software supply chains. The organizations that thrive will be those that accept this reality and invest heavily in the defensive infrastructure that allows them to observe, adapt, and respond faster than the adversary can evolve.

Institutionalizing Vigilance as a Core Business Function

The ultimate takeaway from the current threat landscape is that cybersecurity can no longer be sequestered into a back-office IT department. It must be elevated to a board-level priority that dictates how the company handles everything from vendor selection to product development. When leadership treats security as a checkbox, they are fundamentally misunderstanding the existential risk that these automated threats pose to their market position and operational integrity. I see this reality manifesting in the increasing frequency of leadership turnover within organizations that fail to treat security as a first-order business risk. If you are not integrating security into your organizational DNA, you are building your future on a foundation that is already actively being undermined by adversaries. Establishing a culture of vigilance means fostering a workforce that is trained to recognize the signs of deception, ensuring that security-by-design is non-negotiable for every engineering team, and maintaining a budget that reflects the severity of the threat landscape.

Securing the Path Forward in a Hostile Digital Ecosystem

In closing, the path forward is narrow and requires an uncompromising commitment to technical excellence. We cannot afford to be complacent, nor can we afford to trust in the effectiveness of legacy solutions that were never designed to operate against AI-driven adversaries. The future of security is about visibility, automation, and the ruthless elimination of unnecessary trust. It is about building a defense that is as intelligent, distributed, and persistent as the threats we are up against. This is not a short-term project that can be completed and filed away; it is a permanent change in how we operate, build, and interact in the digital world. The landscape will continue to shift, and the tools available to our adversaries will continue to improve, but by focusing on robust identity management, resilient architecture, and an unwavering commitment to data integrity, we can maintain the upper hand. The battle for the digital future is ongoing, and only those who are willing to adapt, innovate, and secure their environments with extreme prejudice will remain standing when the smoke clears.

D. Bryan King

Sources

• CISA Cybersecurity Advisories
• NIST Cybersecurity Framework
• ENISA Threat Landscape Reports
• SANS Institute Security Blog
• Gartner Cybersecurity Research
• CrowdStrike Global Threat Report
• Mandiant M-Trends Report
• Palo Alto Networks Cyberpedia
• Google Security Blog
• Microsoft Security Blog
• IBM Cost of a Data Breach Report
• CIS Critical Security Controls
• Cybereason Defense Blog
• Dark Reading
• The Hacker News
• Recorded Future Intelligence
• Rapid7 Security Blog
• Unit 42 Threat Intelligence
• FireEye Threat Research
• Tenable Research Blog
• AlienVault Security Essentials
• Varonis Data Security Blog
• Proofpoint Security Blog
• Trend Micro Security News
• Check Point Research
• Recorded Future Threat Intelligence
• Kaspersky Daily
• FortiGuard Labs
• Cisco Security Reports
• Splunk Security Blog
• CrowdStrike Blog
• CyberScoop
• SC Media
• ZDNet Security
• BleepingComputer

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

When I introduce someone to Asfaload's solution, I noticed the discussion often follows the same script. That led me to write it down in a post. Take look if you want to understand what Asfaload does and how: https://www.asfaload.com/blog/asfaload-intro/
#buildinpublic #security #softwaresupplychain

When I introduce someone to Asfaload's solution, I noticed the discussion often follows the same script. That led me to write it down in a post. Take look if you want to understand what Asfaload does and how: https://www.asfaload.com/blog/asfaload-intro/
#buildinpublic #security #softwaresupplychain

#Laravel-lang: Supply Chain Attack Targets Laravel-Lang Packages with Credential Stealer #Malware

Attackers injected a credential stealer into 200+ Laravel-lang package versions by pushing tags tied to attacker-controlled forks:

#SoftwareSupplyChain
👇
https://www.aikido.dev/blog/supply-chain-attack-targets-laravel-lang-packages-with-credential-stealer

https://www.wiz.io/blog/mini-shai-hulud-strikes-again-tanstack-more-npm-packages-compromised
#CyberSecurity #InfoSec #SupplyChainSecurity #SoftwareSupplyChain #NPM #OpenSourceSecurity #AppSec #DevSecOps #ThreatIntel #Malware #JavaScript #NodeJS #CICD #GitHubActions #CloudSecurity #TypeScript #ReactJS #WebDev #OpenSource #DevTools #SoftwareEngineering #DeveloperSecurity #SecureCoding #GitHub #SupplyChainAttack #Programming #TechNews #DevOps #ApplicationSecurity #ThreatResearch #SecurityEngineering #CyberAttack #Hackers #MalwareAlert #SecurityResearch #DevCommunity

RubyGems Disrupts Signups Amid Malicious Package Surge

RubyGems has temporarily halted new account registrations amid a significant surge in malicious packages, with security experts warning of a major attack on the platform. The move comes as Mend.io, the organization responsible for securing RubyGems, works to contain the incident.

https://osintsights.com/rubygems-disrupts-signups-amid-malicious-package-surge?utm_source=mastodon&utm_medium=social

#MaliciousPackage #Rubygems #SoftwareSupplyChain #EmergingThreats #Mendio

Security Tip: Transparency is key to a secure software stack. 🛡️ Implementing a Software Bill of Materials (SBOM) allows your team to maintain a comprehensive inventory of all components. When a new vulnerability breaks, an SBOM helps you identify affected systems in minutes, not days. Stay informed on the latest vulnerabilities and remediation steps at https://cvedatabase.com #CyberSecurity #InfoSec #SBOM #SoftwareSupplyChain #CVE

One more #breach that @asfaload prevents: https://www.neowin.net/news/if-you-downloaded-this-popular-software-recently-you-might-have-installed-malware/

Our #opensource #multisig solution is auditable and can be #selfhosted. Check info at https://asfaload.com

Available very soon!

#security #softwaresupplychain #jdownloader @neowindy.bsky.social #buildinpublic

Deployed backend for the first time,and ran an e2e test script on it successfully 🎉 It registered a #github project,registered a release' assets, collected signatures from devs,and made a download of the asset, checking signatures.Happy with the progress! #buildinpublic #security #softwaresupplychain

RE: https://social.lfx.dev/@openssf/116527089393674087

Open infrastructure isn't free. 🌱

Packagist/Composer signed a joint
OpenSSF letter with PyPI, crates, Maven, CPAN, etc on real cost of running package registries.

Packagist needs to finance staff, not just hardware and bandwidth. Contact me if your company's interested in joining our sponsorship program for its launch this month while we work on long term solutions.

#php #phpc #composerphp #softwaresupplychain #PreserveOpenSource #FreeSoftwareIsntFree #OpenSource #Sustainability

CVE Feeds Overlook End-of-Life Software Vulnerabilities

The blind spot in CVE feeds is leaving end-of-life software vulnerabilities flying under the radar, with a staggering 167,286 false negatives identified in 2025 alone. This oversight can have serious consequences, as outdated software can still be exploited, even if it's no longer receiving patches.

https://osintsights.com/cve-feeds-overlook-end-of-life-software-vulnerabilities?utm_source=mastodon&utm_medium=social

#EndoflifeSoftware #Cve #VulnerabilityManagement #SoftwareSupplyChain #EmergingThreats

I wonder if there's a software business model where you buy the software for the binary and the source code? The source code is not exactly open, but is available on that specific version. I'm also wondering how that would work for the software supply chain. 🤔

#Software #business #foss #oss #intelectualProperty #sourcecode #development #developers #SoftwareSupplyChain

Trellix Source Code Repository Breached

Trellix revealed a breach of its source-code repository over the weekend, but fortunately found no signs of exploitation or compromise to its code release process. The company is still investigating and has promised to share more details once it's completed.

https://osintsights.com/trellix-source-code-repository-breached?utm_source=mastodon&utm_medium=social

#SourceCodeBreach #Trellix #ExtendedDetectionAndResponse #EmergingThreats #SoftwareSupplyChain

Trellix Breach Exposes Source Code Repository

Trellix has confirmed a security incident involving unauthorized access to part of its source code repository, and is working closely with forensic experts and law enforcement to investigate. The company is reviewing the breach and will share updates as more information becomes available.

https://osintsights.com/trellix-breach-exposes-source-code-repository?utm_source=mastodon&utm_medium=social

#TrellixBreach #SourceCodeExposure #CybersecurityIncident #EmergingThreats #SoftwareSupplyChain

Medtronic Discloses Cyber Breach by ShinyHunters Gang

Medtronic recently reported a cyber breach by the ShinyHunters gang to federal authorities and the SEC, revealing that hackers had infiltrated its corporate IT system. Fortunately, the company has found no evidence that patient safety or electronic connections to customers were compromised.

https://osintsights.com/medtronic-discloses-cyber-breach-by-shinyhunters-gang?utm_source=mastodon&utm_medium=social

#Healthcare #Medtronic #Shinyhunters #CyberBreach #SoftwareSupplyChain

Cloudsmith Bolsters Software Supply-Chain Security with $72M Raise

Cloudsmith just secured $72 million to supercharge its artifact management platform and take software supply-chain security to the next level. With a strong artifact management layer in place, companies can enjoy the added benefit of a secure software supply chain.

https://osintsights.com/cloudsmith-bolsters-software-supply-chain-security-with-72m-raise?utm_source=mastodon&utm_medium=social

#SoftwareSupplyChain #ArtifactManagement #FundingRound #SeriesC #Cloudsmith

Asfaload can now use your ed25519 #ssh keys to sign artifacts! No additional key to manage for Asfaload. https://github.com/asfaload/asfaload
#security #softwaresupplychain

The EU’s Cyber Resilience Act (CRA) is a “GDPR moment” for #SoftwareSecurity.

In this #InfoQ #podcast, Viktor Peterson explores how the CRA is reshaping expectations for software producers & supply chain compliance.

Key highlights:
✅ Why SBOMs are operational assets
✅ The danger of "weaponized code" in your security tools
✅ The shift toward vendor-neutral discovery

🎧 Listen now: https://bit.ly/429icwC

📄 #transcript included

#CyberSecurity #SBOM #SoftwareSupplyChain #Compliance

Recent software supply chain attacks - yowers!

In March, popular open source tools Trivy and Axios were compromised with malware, and we won't know the full blast radius for months.

Axios was breached by North Korean hackers who turned it into a malware delivery vehicle for about three hours after attackers hijacked a maintainer's account and slipped a remote-access trojan (RAT) into two seemingly legitimate releases.

Trivy was hacked by a loosely knit band of hackers called TeamPCP, who injected credential-stealing malware.

"Attackers are starting to really look at the supply chain and open source packages, and figure out ways to compromise developers to deliver malware or gather data" ... https://www.theregister.com/2026/04/11/trivy_axios_supply_chain_attacks/ #Hackers #Malware #Software #OpenSource #SoftwareSupplyChain #Trojan #CyberSecurity #Security #Trivy #Axios

Securing the container was never the whole answer. The application dependencies inside it were always the risk.

In 2026, that gap has a name and a price tag.

https://www.linkedin.com/pulse/view-from-trenches-why-software-supply-chain-still-liability-7qrme/

#OpenSourceSecurity #SoftwareSupplyChain #CyberSecurity

Not sure it is the right order: our documentation is deployed before our backend is even online :-D
https://www.asfaload.com/doc/
The fastest way to deploy the doc was using https://rust-lang.github.io/mdBook/ , incidentally a #rustlang project like us.
#buildinpublic #mdbook #security #softwaresupplychain

5 reasons your open source software strategy is a personal liability in 2026.
AI code volume broke the scan-and-pray model. Here's what's left exposed.

https://medium.com/@ActiveState_ASPM/the-five-horsemen-of-the-ai-code-apocalypse-why-your-current-open-source-software-strategy-is-a-78f5b7efe162

#OpenSourceSecurity #SoftwareSupplyChain #CyberSecurity

AI pulls open source dependencies faster than humans can vet them. The perimeter was never the problem.

The ingredients were.

We broke down where application layer security actually stands in 2026.

https://substack.com/home/post/p-193372464

#OpenSourceSecurity #SoftwareSupplyChain #CyberSecurity