
Security News
New React Server Components Vulnerabilities: DoS and Source Code Exposure
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.

A node.js API module and CLI for searching your code for comments referencing JIRA tickets and looking up their current status.
I use tickets after each new release of Appcelerator's Titanium to see if it fixes issues I have worked around in my code. This is also where the defaults for this module come from. However, you can override any of them easily via the listed options.
A screencast showing the CLI in action:

$ sudo npm install -g tickets
Type tickets -h to see the options:
-d, --dir <value> directory to search in [default: process.cwd()]
-e, --extensions <items> comma-separated list of file extensions or + for all
[default: js,jmk,tss,xml]]
-k, --keys <items> comma-separated list of JIRA project keys or + for all
[default: TIMOB,ALOY]
-j, --jira <value> url of the JIRA install to query
[default: https://jira.appcelerator.org/]
OR
reapeatable jira configuration
[example: user:password@http://jira.company.com/:KEY1,KEY2 ]
-u, --username <value> optional username to login to JIRA
-p, --password <value> optional password to login to JIRA
You can also use tickets as a module. It exports just a single function which you can call with an object containing any of the options and a callback to receive the error or found issues.
An example inspired by @manumaticx to use as a Grunt task:
grunt.registerTask('tickets', 'Checking for referenced JIRA tickets that are closed', function() {
var done = this.async(),
tickets = require('tickets');
tickets({
dir: 'app',
extensions: 'js,tss,xml', // takes both CSV and
keys: ['ALOY', 'TC'] // Array
}, function(err, issues) {
if (err) {
grunt.log.error(err);
} else {
issues.forEach(function(issue) {
if (!issue.error && issue.fields.status.name === 'Closed') {
var versions = [];
var files = [];
issue.fields.fixVersions.forEach(function(version) {
versions.push(version.name + ' (' + version.releaseDate + ')');
});
for (var file in issue.files) {
files.push(file + ' #' + issue.files[file].join(', #'));
}
grunt.log.writeln();
grunt.log.writeln(' Issue: ' + issue.key);
grunt.log.writeln('Versions: ' + versions.join(', '));
grunt.log.writeln(' Files: ' + files.join(', '));
}
});
}
done();
});
});

[sudo] npm install -g grunt-cligit clone https://github.com/fokkezb/tickets.git && cd tickets && npm installgrunt testPlease report issues and features requests in the repo's issue tracker.
Distributed under MIT License.
FAQs
Retrieves the state of JIRA tickets refered to in your code.
The npm package tickets receives a total of 1 weekly downloads. As such, tickets popularity was classified as not popular.
We found that tickets demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.

Security News
Socket CEO Feross Aboukhadijeh joins Software Engineering Daily to discuss modern software supply chain attacks and rising AI-driven security risks.

Security News
GitHub has revoked npm classic tokens for publishing; maintainers must migrate, but OpenJS warns OIDC trusted publishing still has risky gaps for critical projects.