Result:
found more than 673 distributions - search limited to the first 2001 files matching your query
( run in 0.728 )
App-Image-Generator
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Images-To-DjVu
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Info
view release on metacpan or search on metacpan
lib/App/Info.pm view on Meta::CPAN
}
return $self->{version};
}
Finally, the C<confirm()> method should be used to verify core pieces of data
that significant numbers of other methods rely on. Typically such data are
executables or configuration files from which will be drawn other meta data.
Most often, such major data points will be sought in the object constructor.
Here's an example:
App-IsGitSynced
view release on metacpan or search on metacpan
bin/is_git_synced view on Meta::CPAN
my $has_divergences_with_origin;
foreach my $branch (@branches) {
next if $branch eq '(no branch)';
next if $branch =~ /(detached .*)/;
my $local = `cd $path; git rev-parse --verify $branch 2>&1`;
my $origin = `cd $path; git rev-parse --verify origin/$branch 2>&1`;
$has_divergences_with_origin = $TRUE if $local ne $origin;
}
if (not $has_divergences_with_origin) {
App-KGB
view release on metacpan or search on metacpan
* declare test dependencies in test_requires
* client: add --debug option
* git client: chomp git-config-determined config file path before usage
* replace ~~ (smartmatch) usage. ~~ is deprecated in perl 5.18
* replace given/when usage, declared experimental in perl 5.18
* client: verify config file structures
* git client: do not die on unknown ref updates (see #706375)
* git client: squash creation if numerous tags (>5 currently)
* git client: configurable tag squash threshold/message
* client: correct POD about Client->format_message arguments
* bot: allow setting of "" color to disable colouring of a given item
App-Kramerius-To-Images
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Kramerius-URI
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Kramerius-V4
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-LDAP
view release on metacpan or search on metacpan
0.03 Thu Dec 02 11:56:34 2010
- be able to $ ldap del user <username>
0.02 Thu Dec 02 01:34:20 2010
- verify user via UID
- be able to $ ldap import ldif_files
0.01 Wed Nov 24 15:11:39 2010
- original version
App-LXC-Container
view release on metacpan or search on metacpan
t/mockup-files/dpkg.status view on Meta::CPAN
Essential: yes
Status: install ok installed
Architecture: amd64
Depends: tar (>= 1.28-1)
Pre-Depends: libbz2-1.0, libc6 (>= 2.34), liblzma5 (>= 5.4.0), libmd0 (>= 0.0.0), libselinux1 (>= 3.1~), libzstd1 (>= 1.5.2), zlib1g (>= 1:1.1.4)
Suggests: apt, debsig-verify
Package: evince
Status: install ok installed
Architecture: amd64
Depends: evince-common (>= 43.1-2), gsettings-desktop-schemas, libevdocument3-4 (= 43.1-2+b1), libevview3-3 (= 43.1-2+b1), shared-mime-info, dconf-gsettings-backend | gsettings-backend, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.34), libcairo-gobject2 (>= ...
App-Licensecheck
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.93.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Count
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Field008
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Filter
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Leader
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-List
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Record-Stats
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Validator-Report
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MARC-Validator
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-MFILE-WWW
view release on metacpan or search on metacpan
bin/mfile-www view on Meta::CPAN
=item * if already running as root, the symlinks are created and the
script displays a message asking to be re-run without --init as a normal user
=item * once the symlinks are in place, the script runs some sanity
checks (mainly verifying the existence of certain files in their
expected places)
=back
=item * the script calls the C<App::MFILE::WWW::init> routine, which loads
App-MHFS
view release on metacpan or search on metacpan
lib/MHFS/HTTP/Server.pm view on Meta::CPAN
if(! $csock) {
say "server: cannot accept client";
return 1;
}
# gather connection details and verify client host is acceptable
my $peerhost = $csock->peerhost();
if(! $peerhost) {
say "server: no peerhost";
return 1;
}
App-MakeEPUB
view release on metacpan or search on metacpan
examples/rfc/README.pod view on Meta::CPAN
=back
=head2 Check your EPUB ebook
If you happen to have installed epubcheck you can verify the EPUB
epubcheck rfc2328.epub
If there are any problems with the HTML in the ebook,
try to repair them by adjusting the script I<< bin/finish-htmlrfc.pl >>.
App-MatrixClient
view release on metacpan or search on metacpan
lib/App/MatrixClient/Matrix.pm view on Meta::CPAN
$self->{matrix} = Net::Async::Matrix->new(
server => $args{server},
( $args{ssl} ? (
SSL => 1,
SSL_verify_mode => 0,
) : () ),
on_log => $dist->curry::fire_sync( 'log' ),
on_presence => sub {
App-MatrixTool
view release on metacpan or search on metacpan
lib/App/MatrixTool/Command/notary.pm view on Meta::CPAN
use base qw( App::MatrixTool );
our $VERSION = '0.08';
use MIME::Base64 qw( decode_base64 );
use Protocol::Matrix qw( verify_json_signature );
use constant DESCRIPTION => "Fetch a server's signing key via another server";
use constant ARGUMENTS => ( "server_name", "via" );
=head1 NAME
lib/App/MatrixTool/Command/notary.pm view on Meta::CPAN
$self->output( "Keys from $result->{server_name} via notary $via" );
$self->output();
my $store = $self->server_key_store;
foreach my $key_id ( keys %{ $result->{verify_keys} } ) {
my $key = decode_base64 $result->{verify_keys}{$key_id}{key};
$self->output( "Key id $key_id" );
$self->output( " " . $self->format_binary( $key ) );
my $ok;
foreach my $signing_server ( keys %{ $result->{signatures} } ) {
foreach my $signing_key_id ( keys %{ $result->{signatures}{$signing_server} } ) {
my $signing_key = $store->get( server => $signing_server, id => $key_id );
next unless defined $signing_key;
my $verified = eval { verify_json_signature( $result,
public_key => $signing_key,
origin => $signing_server,
key_id => $signing_key_id,
); 1 };
App-MechaCPAN
view release on metacpan or search on metacpan
lib/App/MechaCPAN/Install.pm view on Meta::CPAN
'Configuring' => \&_config_prereq,
'Configuring' => \&_configure,
'Configuring' => \&_mymeta,
'Prerequisites' => \&_prereq,
'Prerequisites' => \&_test_prereq,
'Prerequisites' => \&_prereq_verify,
'Building' => \&_build,
'Testing' => \&_test,
'Installing' => \&_install,
'Installed' => \&_write_meta,
);
lib/App/MechaCPAN/Install.pm view on Meta::CPAN
}
return @deps, $target;
}
sub _prereq_verify
{
my $target = shift;
my $cache = shift;
my @deps = _target_prereqs( $target, $cache );
App-Milter-Limit-Plugin-BerkeleyDB
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.80.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Milter-Limit-Plugin-SQLite
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.80.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Milter-Limit
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.93.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Mimosa
view release on metacpan or search on metacpan
root/js/ext-3.3.1/ext-all.js view on Meta::CPAN
* Ext JS Library 3.3.1
* Copyright(c) 2006-2010 Sencha Inc.
* licensing@sencha.com
* http://www.sencha.com/license
*/
(function(){var h=Ext.util,k=Ext.each,g=true,i=false;h.Observable=function(){var l=this,m=l.events;if(l.listeners){l.on(l.listeners);delete l.listeners}l.events=m||{}};h.Observable.prototype={filterOptRe:/^(?:scope|delay|buffer|single)$/,fireEvent:fu...
/* SWFObject v2.2 <http://code.google.com/p/swfobject/>
is released under the MIT License <http://www.opensource.org/licenses/mit-license.php>
*/
var swfobject=function(){var F="undefined",t="object",U="Shockwave Flash",Y="ShockwaveFlash.ShockwaveFlash",s="application/x-shockwave-flash",T="SWFObjectExprInst",z="onreadystatechange",Q=window,l=document,v=navigator,V=false,W=[i],q=[],P=[],K=[],n,...
App-Module-Lister
view release on metacpan or search on metacpan
=head2 GitHub Attestations
This distribution now uses
L<GitHub Attestations|https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/>,
which allow you to verify that the archive file you have was made from
the official repo.
You need a GitHub account and the L<gh tool|https://github.com/larsks/ghcli>.
# download the distro file from GitHub, MetaCPAN, or a CPAN mirror
$ gh auth login
...follow instructions...
$ gh attestation verify App-Module-Lister-1.23.tar.gz --owner briandfoy
=head2 Getting help
Although I'm happy to hear from module users in private email,
that's the best way for me to forget to do something.
( run in 0.728 second using v1.01-cache-2.11-cpan-39bf76dae61 )