Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Test::LeakTrace provides several functions that trace memory leaks. This module scans arenas, the memory allocation system, so it can detect any leaked SVs in given blocks.
This module performs various checks on a module's Regexp::Pattern patterns.
This module exports three test functions and four diff-style functions.
Test::Roo provides composable, reusable tests with roles.
Test::Class::Most provides some more convenience when using Test::Class.
This module lets you check your module's namespaces for imported functions you might have forgotten to remove with namespace::autoclean or namespace::clean and are therefore available to be called as methods, which usually isn't want you want.
Test::SharedFork is a utility module for Test::Builder. It makes fork(2) safe to use in test cases.
Test::File::Contents provides functions for testing the contents of files.
Test::DistManifest provides a simple method of testing that a MANIFEST file matches its distribution.
Test::Requires checks to see if the module can be loaded. If this fails, then rather than failing tests this skips all tests.
This module is intended to be used as a drop-in replacement for Test::NoWarnings. It also adds an extra test, but runs this test before done_testing calculates the test count, rather than after. It does this by hooking into done_testing as well as via an END block. You can declare a plan, or not, and things will still Just Work.
This module provides a few convenience methods for testing warning based code.
This module provides some drop-in replacements for the string comparison functions of Test::More, but which are more suitable when you test against long strings.
Tainted data is data that comes from an unsafe source, such as the command line, or, in the case of web apps, any GET or POST transactions. Read the perlsec man page for details on why tainted data is bad, and how to untaint the data.
When you're writing unit tests for code that deals with tainted data, you'll want to have a way to provide tainted data for your routines to handle, and easy ways to check and report on the taintedness of your data, in standard Test::More style.
This Perl testing library focuses on testing and working with XPath expressions, most likely in the context of XML document processing.
Using Test::PerlTidy, any file ending in .pl, .pm, .t or .PL will cause a test fail unless it is exactly as perltidy would like it to be.
When used in a test script Test::Distribution goes through all the modules in your distribution, checks their POD, checks that they compile successfully and checks that they all define a $VERSION. In addition, this module performs a number of tests on the distribution itself. It checks that the distributed files match the SIGNATURE file, if that file exists. It checks that the distribution is not missing any core description files. It also checks that the complete set of pre-requisite packages are listed in the Makefile.PL file.
Fennec ties together several testing related modules and enhances their functionality in ways you don't get loading them individually. Fennec::Lite takes a minimalist approach to do for Fennec what Mouse does for Moose.
Test::Filename provides functions to convert all path separators automatically.
Test::FailWarnings adds test failures if warnings are caught.
Test::Base gives a way to trivially write your own test framework base class. It concentrates on offering reusable data driven patterns, so that you can write tests with a minimum of code.
Test::Portability::Files module is used to check the portability across operating systems of the names of the files present in the distribution of a module. The tests use the advices given in 'Files and Filesystems' in perlport. The author of a distribution can select which tests to execute.
Test::RunValgind checks weather Valgrind does not detect errors (such as memory leaks) in an arbitrary binary executable.
Test::MockObject allows you to create objects that conform to particular interfaces with very little code. You don't have to reimplement the behavior, just the input and the output.