Managing software artifacts across distributed teams and complex infrastructures securely demands proactive measures. Robust policy management is the best way to ensure compliance in your software supply chain. Cloudsmith, the leading cloud-native package management platform, can streamline policy management and strengthen security. Let’s explore why policy management matters and how we can simplify it for you.

Policy Management is a structured way to define, implement, and enforce rules and guidelines in your software delivery process. Effective policy management:

Enhances Security: Enforces strict access controls and ensures the integrity of your software artifacts, reducing vulnerabilities and minimizing risks.

Ensures Compliance: Helps you adhere to GDPR, HIPAA, SOC 2, and other regulatory frameworks, keeping you audit-ready.

Maintains Consistency: Standardizes workflows across teams, ensuring that everyone operates within established guardrails.

Boosts Efficiency: Automates policy enforcement, reducing manual overhead for approvals and compliance checks.

For a deeper dive into Cloudsmith's approach to enhancing security and compliance through policy management, check out 

Cloudsmith's Enhanced Security with Policy Management

Cloudsmith Policy Management: A Holistic Approach

With Cloudsmith, you take full control of your package repositories with policy management. These make Cloudsmith the ideal choice for teams prioritizing security and compliance:

You set granular permissions for users, teams, and API tokens. Using role-based access control (RBAC), you can:

Assign repository access based on user roles.

Apply least-privilege principles to ensure users access only what they need.

Monitor and audit access logs to detect anomalies.

Learn more about how Cloudsmith supports Zero Trust security principles in 

Implementing Zero Trust Security with Cloudsmith in 5 Steps

Efficient storage management reduces costs and enhances security. Cloudsmith lets you:

 to automatically remove outdated or unused artifacts after a specified time.

Use Disposal Policies to securely delete artifacts while maintaining an audit trail, ensuring data governance compliance.

Controlling where your data can be stored or accessed is a crucial part of many compliance frameworks. Cloudsmith supports geo-restriction policies, allowing you to:

Restrict repository access based on geographic regions.

Check out how Cloudsmith has helped organizations like SaaS providers comply with GDPR and data residency requirements in our 

 Security Scanning and Vulnerability Policies

To protect your software supply chain, Cloudsmith integrates security scanning directly into the platform. You can:

Block packages with known vulnerabilities.

Automatically notify teams when critical issues are detected.

Licensing compliance is an important part of managing open-source dependencies. With Cloudsmith, you can:

Define acceptable licenses for your projects.

Block artifacts that violate license compliance policies.

Generate reports for audits, ensuring transparency.

Cloudsmith empowers you to automate policy enforcement by integrating with CI/CD pipelines. By embedding policy checks into your workflows, you can:

Automatically validate artifacts against predefined rules.

Prevent deployment of non-compliant artifacts.

Accelerate delivery cycles while ensuring compliance.

To learn how policy enforcement can be integrated into your DevOps workflows, explore 

Kong – Streamlining Artifact Management and Distribution

Kong, a prominent open-source API management platform, required a robust solution to manage and distribute their software artifacts efficiently. By partnering with Cloudsmith, Kong was able to:

Centralize Artifact Storage: Utilize Cloudsmith's universal artifact management to store all their packages in a single, secure location.

Implement Fine-Grained Access Controls: Define and enforce policies that ensure only authorized personnel have access to specific repositories and artifacts.

Enhance Distribution Efficiency: Leverage Cloudsmith's global edge caching to deliver artifacts swiftly to their global user base.

This collaboration resulted in a more streamlined and secure artifact management process, allowing Kong to focus on developing their core products without worrying about the complexities of artifact distribution.

Best Practices for Policy Management in Cloudsmith

Policy management is even more powerful with some planning, collaboration, and continuous improvement. Here are some best practices to help you maximize the value of Cloudsmith policy management:

Your security, compliance, and development teams can establish policies that align with your organization’s goals. Consider these steps:

Identify Key Objectives: Are you looking to adhere to regulatory requirements like SOC 2? Or reduce security vulnerabilities in production?

Collaborate Across Teams: Involve stakeholders from DevOps, security, and legal teams to ensure policies cover access control, licensing, and vulnerability scanning.

Create a Policy Library: Maintain a centralized repository of all approved policies so it’s easy for teams to reference and follow them.

Pro Tip: Use policy templates and the Enterprise Policy Manager to standardize and scale policy creation across multiple teams. Learn more about Cloudsmith's 

Continuous monitoring helps you stay ahead of potential risks and ensure compliance over time. Cloudsmith offers built-in monitoring tools to help you track and report policy adherence. To maximize their effectiveness:

Audit Regularly: Leverage Cloudsmith’s Audit Logs to monitor actions performed by users, systems, and service accounts. This feature provides a complete history, enabling you to identify anomalies and ensure compliance.

Track Key Metrics: Monitor metrics like artifact vulnerability rates, license violations, and geographic access patterns to stay proactive in your security efforts.

Set Alerts: Configure notifications for critical issues, such as non-compliant artifacts or unauthorized access attempts, so your team can respond quickly.

For more details, check out Cloudsmith’s guide to 

By embedding policy checks into your DevOps workflows, you can maintain compliance without slowing down delivery. Here’s how:

Automate Artifact Validation: Use Cloudsmith’s APIs to automatically validate artifacts against predefined policies during your CI/CD pipeline runs.

Prevent Non-Compliant Deployments: Configure your CI/CD tools to block deployments that fail security or compliance checks, ensuring that only approved artifacts make it to production.

Leverage Pipeline Integration: Integrate Cloudsmith with popular CI/CD tools like CircleCI, GitHub Actions, and GitLab to streamline policy enforcement.

For more information on managing package promotion workflows, check out 

How to Manage Your Package Promotion Workflows with Cloudsmith

By automating policy enforcement, your team can accelerate delivery cycles while maintaining security and compliance.

Your policies need to keep pace with change. Regularly reviewing and updating your policies ensures they remain relevant and effective. Follow these best practices:

Schedule Regular Audits: Conduct quarterly policy audits to ensure they align with current regulations and organizational goals.

Adapt to New Threats: Stay informed about emerging vulnerabilities and security risks, updating your policies to address them.

Solicit Feedback: Encourage teams to share their experiences with existing policies and suggest improvements. This collaborative approach fosters a culture of compliance and innovation.

Document Changes: Maintain a change log for your policies to track updates and communicate them effectively across the organization.

Pro Tip: Use Cloudsmith’s reporting features to generate compliance reports that provide valuable insights and help refine your policies over time.

Stay up-to-date with Cloudsmith’s latest features and updates by joining our 

Ready to empower secure and compliant software delivery? Book a 

 with an expert today and see how Cloudsmith transforms your software artifact management.

Maia Livingstone

Campaign Manager

Secure and Compliant Software Delivery with Cloudsmith Policy Management

2024 was a year of incredible stories. At Cloudsmith, we had the privilege of being part of our customers' journeys as they reached significant milestones, driving growth, innovation, and strengthened trust across the globe. Our customers led the way, leveraging Cloudsmith’s capabilities to enhance their workflows, scale their operations, and secure their software supply chains. Let’s explore the amazing progress our community made together and the stories behind these achievements.

In 2024, our customers embraced the all-new WebApp, a major upgrade designed to make artifact management more intuitive and efficient. This enhanced user experience enabled teams to streamline their operations and focus on delivering value to their customers.

Throughout the year, more and more teams turned to Cloudsmith, resulting in a staggering 53% increase in packages delivered. Each delivery represented a project moving forward, a product getting closer to market, or a team achieving its goals. This growth was a testament to the trust our customers placed in Cloudsmith as their reliable partner in artifact management.

2024 was the year where our customers gained unprecedented control over their software supply chains. With the introduction of Broadcasts and Policy Management, teams were empowered to oversee their operations with greater clarity and precision. These features were catalysts that enabled our customers to work smarter and safer in an ever-evolving digital landscape.

This year, our customers met us at events like KubeCon, GitHub Universe, and SREcon. These weren’t just conferences - they were chances to learn, share, and grow together. Our customers brought their experiences and challenges to the table, and together, we explored new ways to innovate and push the industry forward.

For teams integrating Cloudsmith with tools like Azure DevOps and ArgoCD, 2024 was about making life easier. These integrations weren’t just about technology - they were about creating seamless workflows that allowed teams to focus on their goals, knowing their tools would support them every step of the way.

Throughout the year, our customers’ success was our top priority. With a 96.8% customer support satisfaction rating, every interaction aimed to empower users and solve challenges swiftly. Behind each support ticket resolved was a team able to move forward with confidence, knowing Cloudsmith had their back.

We measure success not only through metrics but also by the impact we've had on our customers' businesses. Here’s what a few of them had to say about their experiences with Cloudsmith in 2024:

“Cloudsmith has significantly simplified our artifact management. By using Cloudsmith, we can easily store and share artifacts across the organization, while also ensuring the security and compliance of every release. It’s been a true partner in our growth.”– Sandy McNeely, Director of DevOps, PagerDuty

“Cloudsmith’s solution has made a noticeable difference in our workflow. We’ve streamlined the way we manage and distribute software artifacts, and the speed and reliability have been key in helping us meet our goals.”– Tom Dillon, Senior VP of Engineering, Diligent

“Using Cloudsmith allowed us to ensure our products were shipped more securely and efficiently. The ability to have fine-grained control over our software supply chain means we can focus on building innovative solutions while Cloudsmith handles the infrastructure.”– Chris Sutherland, CEO & Founder, Humanising Autonomy

“Cloudsmith has been integral in supporting our continuous delivery pipeline. The easy integration and flexibility it offers have significantly enhanced the speed at which we can release new features and improvements.”– Matt 

As we move into 2025, we’re excited to keep building alongside our customers. Their stories drive us to innovate, improve, and support them even better. To all the teams we work with - thank you for an amazing 2024.

Want to see what’s next? Join us on our journey in 2025 by exploring our latest updates and features or by booking a 

Cloudsmith 2024: By the Numbers

What a year it’s been at Cloudsmith. As we look back on 2024, it’s hard not to feel a sense of pride - and even a little awe - at how far we’ve come. From a scrappy startup to a trusted partner for some of the biggest names in the world, this year has been a turning point, both for our company and the people who make it special.

In this video, our CEO, Glenn Weinstein, reflects on the highs, the challenges, and the moments that defined this year for us. Here’s a little glimpse into what made 2024 unforgettable.

Coffee with Cloudsmith 2024

Growing Up Without Losing Who We Are 🌱🏢

We’ve doubled our count of Cloudsmithers in 2024! It’s exciting, of course, but also a little bittersweet. It’s harder to fit everyone into a room these days - we’d need a really big room! - and keeping up with all the new names can be a challenge. But growth means something important: we’re helping more people, solving bigger problems, and making a real difference for our customers.

Our mission hasn’t changed - to make developers’ lives easier. What’s shifted is our focus. Over the past 18 months, we’ve zeroed in on enterprises, especially those with massive teams using countless tools, languages, and formats. Cloudsmith’s strength is bringing all that chaos together in one place, making it simpler, faster, and more secure to build great software.

A Team That Feels Like Family 👩‍💻👨‍💻❤️

One of the things that sets Cloudsmith apart is the people. Early on, we were all generalists - pitching in wherever we were needed. But this year, we’ve started to mature, hiring specialists with deep expertise who can push us to the next level.

And while our roots are firmly in Belfast, where Cloudsmith began, we’ve expanded to Dublin, London, other locations around Ireland and the UK, as well as India and the United States, too. Belfast, though, holds something special - it’s become home for many of us, including our New York-born CEO, Glenn Weinstein.

Glenn, who splits his time between the U.S. and Belfast, shares in the video how much he’s come to love the city. “There’s something about walking the streets of Belfast, grabbing dinner, or just soaking up the atmosphere that makes you feel welcome,” he says. “As someone from New York, I never imagined Belfast would feel like home, but it truly does.”

Even though we’re a remote-first team, we believe in the magic of in-person connection. That’s why we bring everyone together three times a year for offsites in Belfast. Those few days - full of laughs, ideas, and even a pint or two - are what fuel the trust and camaraderie that make Cloudsmith such a unique place to work.

For our Engineering team, 2024 has been a year of transformation. What used to be a single team now includes specialized squads like Bytebusters, Sentinel, Platform, and Kronos. These groups allow us to go deeper into what we’re building, whether it’s improving security, expanding formats, or creating a sleek new web app that’s already winning over customers.

Looking ahead to 2025, the roadmap is ambitious - and that’s putting it mildly. From digital signatures to advanced policy management tools, we’re diving headfirst into solving some of the biggest challenges in the software supply chain. It’s a big task, but one we’re excited to tackle.

If there’s one thing that’s really hit home this year, it’s this: our customers don’t just need great software - they need a partner. As we’ve worked with Global 2000 and Fortune 500 companies, we’ve realized that onboarding isn’t just about flipping a switch. It’s about walking alongside them, helping them adapt, and making sure every team - whether it’s five people or 500 - feels supported.

This has been a game-changer for us. We’re not just delivering a product; we’re building relationships. And those relationships? They’re built on trust, understanding, and a commitment to helping our customers succeed.

As we close out 2024, we feel like we’re just getting started. Yes, we’ve grown. Yes, we’ve achieved incredible things. But our dreams are bigger than ever. Glenn Weinstein puts it perfectly: “Cloudsmith isn’t just a feature or a niche. We’re building something foundational, something that will change how enterprises everywhere manage their software supply chains.”

We believe Cloudsmith can be a cornerstone for enterprises - a platform that simplifies, secures, and transforms how software is built. We’re still on the journey, still learning, still growing. And we’re so grateful to everyone who’s been part of it - our team, our customers, and our community.

Watch the video above to hear more from Glenn Weinstein about this incredible year and what’s ahead. And if you’re curious about how Cloudsmith can help your team, we’d love to show you.

Here’s to 2025 and everything it holds. Let’s build it together. 💪✨

A Year to Remember: Cloudsmith’s Journey Through 2024  🚀🌍

Last month, Datadog announced an interesting and useful new feature they call the 

. It offers a real-time scanning approach that identifies vulnerabilities as developers pull packages from public registries like npmjs. It highlights the broader challenge organizations face when securing their software supply chain: managing risk consistently and efficiently at scale.

Anything that helps developers choose better, more secure open source packages is a good thing. That said, the Cloudsmith perspective on this would be that once you get beyond individual developers or small teams, it makes sense to create curated repositories - a proactive, centralized way to manage packages and enforce security policies. Let’s compare the two approaches.

What Datadog’s Supply-Chain Firewall Offers

Datadog’s SCFW intercepts and scans packages from public repositories in real time as developers pull them into their projects. This allows developers to get immediate feedback about vulnerabilities.

Real-Time Scanning: Developers are alerted about vulnerabilities as soon as they pull a package, reducing the risk of introducing issues further down the development pipeline.

Pluggable Scanning Architecture: SCFW allows integration with different scanning engines, offering some flexibility for developers to tailor the tool to their needs.

SCFW focuses on individual package decisions during development. This works great at the individual developer level. For larger organizations, you’re probably going to need a more scalable solution to supply chain security. Here’s where just using SCSW would fall short in a larger organization -

No Persistent Package Management:SCFW focuses on scanning in real time rather than managing a persistent, curated list of approved packages. Without a centralized repository, decisions about which packages and vulnerabilities are acceptable must be made repeatedly, often by individual developers.

Inconsistent Security Decisions:Developers are tasked with deciding whether a vulnerability is acceptable. This can result in inconsistent decisions across teams - two developers may allow or block the same package based on personal judgment. For larger teams, this can become unmanageable without centralized oversight.

Lack of Policy Enforcement:SCFW lacks a policy engine to define and enforce consistent rules for what constitutes an acceptable package. Without a policy framework, decisions are made on a case-by-case basis, which can increase the risk of vulnerabilities slipping through.

Scalability Concerns:As teams and projects grow, real-time scanning could impact performance, particularly if a high volume of packages is being pulled. For organizations with complex pipelines, this may create bottlenecks.

Limited Package Format Support:Currently, SCFW supports only a limited set of package formats (e.g., npm). Modern software teams typically work across multiple formats - such as Docker, Maven, PyPI, and others - which requires broader support.

The alternative to this is curated repositories. Rather than pulling directly from public sources, developers retrieve packages from trusted, centralized repositories that are managed and approved by their organization’s security team. Why is that better?

Centralized and Persistent Security Control:With curated repositories, security teams or DevSecOps professionals define and maintain a trusted list of approved packages. Developers no longer need to assess vulnerabilities individually - every package pulled is already vetted, reducing risk and eliminating inconsistent decision-making.

Policy-Driven Automation:Cloudsmith supports policy enforcement that automates decision-making about which packages are allowed. Security teams can set clear rules, such as blocking known vulnerabilities or restricting certain versions, and those policies are consistently applied across the organization.

Scalability at Enterprise Levels:Cloudsmith is designed to scale seamlessly. Curated repositories ensure fast, efficient access without performance bottlenecks.

Support for Multiple Package Formats:Cloudsmith (and other platforms like ours) supports a wide range of formats - including npm, Docker, Maven, PyPI, NuGet, and more - ensuring all teams can centralize their artifacts and manage security consistently, regardless of the technologies they use.

Reduced Developer Burden:By shifting security decisions to a centralized repository and automated policies, Cloudsmith removes the need for developers to manually assess vulnerabilities. This allows teams to focus on building software, confident that they’re pulling packages from a secure, trusted source.

Real-time vulnerability scanning, like Datadog’s SCFW, is an innovative approach for identifying risks early in the development process. We love seeing this kind of innovation to solve what are becoming increasing urgent issues in securing the software supply chain. That said, for larger organizations, it’s not quite a complete solution.

Thoughts on Datadog’s new Supply-Chain Firewall

Migrating from JFrog Artifactory to a new artifact management platform like Cloudsmith can feel like a daunting task. We promise, it’s actually easier and more straightforward than you think! Many organizations have successfully completed migrations away from JFrog Artifactory, even with complex setups and dependencies. With a well-planned approach and some help following best practices for Artifactory migration, the process becomes seamless.

This guide provides a step-by-step JFrog Artifactory migration strategy and highlights why Cloudsmith is one of the best JFrog Artifactory alternatives.

Why Plan Your JFrog Artifactory Migration?

Migration is basically two things: moving data and re-evaluating workflows. Cloudsmith offers numerous advantages that streamline JFrog migration and ensure your tools align with your long-term goals. With a successful migration, you’ll even minimize downtime and maintain business continuity.

Steps to a Successful JFrog Artifactory Migration

Before beginning your migration from JFrog artifactory, take stock of your current environment:

Identify all hosted repositories and ensure they are up to date.

You may want to take this opportunity to remove unused or outdated artifacts to simplify the migration process. (Note, this is NOT required, and it may be easier and less risky to just move everything.)

Note any upstream repositories and registries, third-party integrations, and workflows that are dependent on your current setup.

2 - Export Your Artifacts from JFrog Artifactory

Exporting artifacts is the first technical step in migrating from JFrog Artifactory. There are three basic approaches:

 Export repositories directly through the Artifactory UI.

 Use CLI commands to export specific packages or repositories.

 This powerful tool automates critical aspects of migration, including ensuring your repositories are correctly organized in the new environment (Repository Structure Mapping) and retaining important data during the transfer (Metadata Preservation) to avoid manual updates post-migration.

After exporting, the next step is importing your artifacts into Cloudsmith:

 Create your organization and repositories in Cloudsmith, aligning them with your intended structure and best practices. This ensures a clean, scalable setup that supports various formats (e.g., Docker, PyPi, NPM).

 Use the Cloudsmith CLI to streamline the import process, allowing you to efficiently upload multiple artifacts in bulk. Automation tools and CI/CD integrations further enhance this workflow by ensuring consistency in artifact management.

 Ensure that metadata, including version history and dependency information, is maintained during the import process. Preserving metadata is crucial for traceability and accountability, especially as you scale your projects and collaborate across teams​

For optimal management, it's essential to follow best practices for repository and package workflows, such as maintaining clear versioning, ensuring secure access control, and leveraging automation for repeatable processes. These practices help streamline workflows, improve security, and ensure consistency in artifact management.

4 - Update Your Build Tools and Integrations

Reconfigure your development tools to integrate with Cloudsmith:

 Update endpoints in your pipelines to push and pull from Cloudsmith.

 Set up upstreams in Cloudsmith to cache and manage third-party libraries from sources like DockerHub, Chainguard, and PyPi.

 Ensure secure access by configuring advanced authentication methods such as Single Sign-On (SSO), OpenID Connect (OIDC), and API tokens. Additionally, define user roles to manage permissions and maintain a robust security framework.

5 - Validate Your JFrog Artifactory Migration

This is a good time to validate your setup to ensure everything is working as expected:

 Confirm that all packages and metadata are present and accessible in Cloudsmith.

Test your pipelines to ensure seamless integration with Cloudsmith.

 Address discrepancies early to avoid complications post-migration.

At this point, you will have a performant, secure, highly available single source for all the artifacts and containers flowing into your organization. If you need any assistance, our friendly support team is always ready to help ensure your migration is smooth and successful.

Once Cloudsmith is fully operational, safely phase out your old Artifactory system:

 Retain logs and critical data for compliance and historical reference.

 Disconnect tools and workflows tied to Artifactory.

Why Choose Cloudsmith as a JFrog Artifactory Alternative?

Cloudsmith is designed to meet the demands of modern software development. It supports all major package types, offers advanced security features, and simplifies artifact management with a fully managed, cloud-native solution. By switching to Cloudsmith, you can reduce infrastructure overhead, streamline workflows, and scale effortlessly with your needs.

Migrating from JFrog Artifactory to Cloudsmith offers significant advantages:

 Manage all your artifacts in one place, from Alpine to Docker to Python to Terraform Modules (32 formats in all).

 Reduce the total cost of ownership and infrastructure overhead with a fully managed service.

 Benefit from features like signing keys and entitlement tokens to enhance control over the distribution and use of your artifacts.

 Add teams, formats, repositories, upstreams, and geographies without worrying about infrastructure, with a platform built for growth.

Start Your JFrog Artifactory Migration Today!

Migrating your artifact management system is easy, and we’re here to make it even easier. Book a meeting with our experts to discuss your unique needs and learn how Cloudsmith can simplify and enhance your workflows.

"Out of all of the vendors we talked to, Cloudsmith was the one that seemed to want to work with us the most. Right away they were saying, 'Here are all the things we want to do for you. Here are the things we can build…' That won us over. And everything that’s happened since then has only confirmed that initial impression."

Master Your JFrog Migration with Cloudsmith

Cloudsmith is more than a repository - it’s a platform designed to empower modern software teams. Start your journey toward streamlined artifact management by connecting with us today. Let’s make your migration a success!

How do I migrate from JFrog Artifactory to Cloudsmith?


Use the Cloudsmith Migration Toolkit to export, import, and validate artifacts, ensuring a smooth JFrog Artifactory migration with minimal downtime.


What are the best practices for Artifactory migration?


Audit repositories, clean up unused data, document dependencies, automate exports, and validate artifacts post-migration for a seamless transition.


Why should I consider JFrog Artifactory cloud migration?


Cloudsmith offers a fully managed, scalable, and secure artifact management solution, reducing infrastructure costs and simplifying workflows.


What are the benefits of using Cloudsmith over JFrog Artifactory?


Cloudsmith provides universal package support, cloud-native efficiency, strong security, and seamless CI/CD integrations for better artifact management.


What tools can I use for JFrog cloud migration?


Use Artifactory’s export tools, JFrog CLI, or Cloudsmith’s Migration Toolkit to automate artifact transfer while preserving metadata.

Mastering Your JFrog Artifactory Migration: Steps to Success

After a focused period of design and development, the new Cloudsmith web app is now available to all customers at 

. The new web app replaces the existing cloudsmith.io, which will be fully decommissioned in 2025.

The new web app is designed to give you a clearer picture of the software flowing into and out of your business:

When you sign in, you'll be presented with crucial information about the health of your Cloudsmith workspace

The new compliance dashboard shows you vulnerabilities and policy violations across your workspace in a unified view

We now aggregate and visualise usage information; the data you store and deliver via Cloudsmith, in a much clearer way

We've made dozens of improvements, small and large, to streamline the day to day administration of your Cloudsmith workspace.

The new web app is backed by significant improvements to our 

. We'll detail these upgrades in a separate post; we've added dozens of new endpoints, making it possible to interact with Cloudsmith programmatically like never before. Automate Everything is a core value of the 

, and we're excited to see what our customers build around our enhanced API.

The new web app is not yet a like-for-like replacement for cloudsmith.io. There are a number of known gaps in the new web app, including:

Discrepancies between usage reporting across the old and new web apps; especially for customers who make heavy use of Docker containers

Signing up or in to the new web app using GitHub or other social logins is not yet available

Client logs/download logs are not visible inside the app

Software licences used across your workspace are not yet being aggregated and visualised

Users can’t upload an avatar, or set an avatar/logo for a workspace

Selecting multiple packages and carrying out bulk actions is not available yet

Cloudsmith Blog

Secure and Compliant Software Delivery with Cloudsmith Policy Management

Cloudsmith 2024: By the Numbers

A Year to Remember: Cloudsmith’s Journey Through 2024 🚀🌍

Thoughts on Datadog’s new Supply-Chain Firewall

Mastering Your JFrog Artifactory Migration: Steps to Success

Launching the new Cloudsmith Web App

Elevating Software Distribution with Cloudsmith’s Broadcasts

Securely Store and Distribute OCI Artifacts

Introducing Cloudsmith’s Advanced Observability Suite for Enterprise Artifact Management

Introducing Cloudsmith’s Enterprise Policy Manager

Your Ultimate KubeCon Guide

Integrating Dependabot with Cloudsmith Using OIDC