azure-pipelines-tasks-packaging-common

v3.246.2

Azure Pipelines Packaging Tasks Common For more information about how to use this package see README

Latest version published 1 month ago

License: MIT

NPM

GitHub

Package Health Score

74 / 100

security
Security review needed
popularity
Small
maintenance
Healthy
community
Active

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
3.246.2	\|	10/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.245.3	\|	09/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.221.1	\|	05/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.198.1	\|	12/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.3	\|	12/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (745)

GitHub Stars: 3.42K
Forks: 2.57K
Contributors: 310

Direct Usage Popularity

The npm package azure-pipelines-tasks-packaging-common receives a total of 745 downloads a week. As such, we scored azure-pipelines-tasks-packaging-common popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package azure-pipelines-tasks-packaging-common, we found that it has been starred 3,418 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: No
Code of Conduct: Yes
Contributors: 310
Funding: No

A good and healthy external contribution signal for azure-pipelines-tasks-packaging-common project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 380
Open PR: 97
Last Release: 1 month ago
Last Commit: 5 months ago

Further analysis of the maintenance status of azure-pipelines-tasks-packaging-common based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that azure-pipelines-tasks-packaging-common demonstrates a positive version release cadence with at least one new version released in the past 3 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 4 years
Dependencies: 16 Direct
Versions: 40
Install Size: 315 kB
Dist-tags: 1
# of Files: 106
Maintainers: 7
TS Typings: No

azure-pipelines-tasks-packaging-common has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

Azure Pipelines Tasks

Tasks

Overview

This repo contains the tasks that are provided out-of-the-box with Azure Pipelines and Team Foundation Server.

This provides open examples on how we write tasks which will help you write other tasks which can be uploaded to your account or server. See Writing Tasks below. Check Deprecation.md file for the list of task which are no longer supported.

Status

	Build & Test
Windows
macOS
Linux

How to Use Tasks

See the documentation for Continuous integration and deployment.

Writing Tasks

If you need custom functionality in your build/release, it is usually simpler to use the existing script running tasks such as the PowerShell or Bash tasks. Writing a new task may be appropriate if you need deeper integration or reusability in many build definitions

Tasks are simply tool runners. They know how to run MSBuild, VSTest, etc... in a first class way and handle return codes, how to treat std/err out, and how to write timeline records based on expected output. They also get access to credentials to write back to TFS/Azure Pipelines.

For uploading custom tasks to Azure Pipelines use the TFS Cross Platform Command Line utility.

Tasks can also be deployed with an Azure DevOps extension. See this tutorial for how to write a custom task and package it inside an extension.

Contributing

This project welcomes contributions and suggestions.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Issues

We accept issue reports both here (file a GitHub issue) and in Developer Community.

Do you think there might be a security issue? Have you been phished or identified a security vulnerability? Please don't report it here - let us know by sending an email to secure@microsoft.com.

azure-pipelines-tasks-packaging-common dependencies

@types/ini @types/ltx @types/mocha @types/node @types/q adm-zip azure-devops-node-api azure-pipelines-task-lib azure-pipelines-tool-lib ini ip-address ltx mocha q semver typed-rest-client

azure-pipelines-tasks-packaging-common development dependencies

typescript

FAQs

What is azure-pipelines-tasks-packaging-common?

Azure Pipelines Packaging Tasks Common. Visit Snyk Advisor to see a full health score report for azure-pipelines-tasks-packaging-common, including popularity, security, maintenance & community analysis.

Is azure-pipelines-tasks-packaging-common popular?

The npm package azure-pipelines-tasks-packaging-common receives a total of 745 weekly downloads. As such, azure-pipelines-tasks-packaging-common popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is azure-pipelines-tasks-packaging-common well maintained?

We found that azure-pipelines-tasks-packaging-common demonstrated a healthy version release cadence and project activity. It has a community of 310 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is azure-pipelines-tasks-packaging-common safe to use?

While scanning the latest version of azure-pipelines-tasks-packaging-common, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 19 October-2024, at 03:24 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP