Use case: Teams working with Maven and NPM packages in Bitbucket Packages need a way to download artifacts (e.g., JARs, WARs) directly from the Web UI for quick inspection or offline testing, as well as upload third-party vendor libraries that are not available in public registries like Maven Central.

Current behavior: Bitbucket Packages does not provide a download or upload option through the Web UI. Artifacts can only be retrieved or published using CLI tools (e.g., mvn, npm, gradle) or through Pipelines automation. While this workflow-first approach works well for CI/CD pipelines, it creates friction for ad-hoc tasks like inspecting a specific artifact version or onboarding vendor-provided dependencies.

Requested behavior:

• Download: Add the ability to download an artifact directly from the Packages UI (e.g., a "Download" button on the artifact version detail page), allowing users to quickly grab a JAR/WAR for local inspection or testing without needing to configure a full Maven/Gradle project.

• Upload: Add the ability to upload artifacts via the Web UI, enabling teams to publish third-party/vendor libraries that don't have source code and aren't available in public registries, without requiring CLI commands.

Impact: Especially useful for teams that manage proprietary or vendor-provided dependencies alongside their own built artifacts. The current CLI-only approach adds unnecessary overhead for simple operations that don't require a full build toolchain. This would lower the barrier to entry for teams adopting Bitbucket Packages for artifact management beyond Docker images.