npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

certificate-recipient

v0.3.0

Published

Recipient of certificates delivered by Certificate Manager Service

Downloads

22

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tristanlstristanls

Keywords

capabilitycapabilityiocertificatemanagercertificaterecipientstore

Readme

certificate-recipient

Stability: 1 - Experimental

NPM version

Recipient of certificates delivered by Certificate Manager Service.

Contents

Installation

The intended usage of certificate-recipient is as part of capability-cli certificate-manager config aws functionality.

To install locally:

npm install certificate-recipient

Usage

This module is intended to be executed as an AWS Lambda function as part of capability-cli certificate-manager config aws functionality that configures this module as well as grants the requisite permissions and creates required supporting infrastructure.

Tests

npm test

Documentation

Recipient.handle(message, context, callback)

  • message: Object Message from Certificate Manager Service delivering a certificate.
    • certificate: String Certificate public key, including intermediate certificate chain, in PEM format.
    • domain: String Domain name for which the certificate is issued.
    • key: String Certificate private key in PEM format.
  • context: Object AWS Lambda context.
  • callback: Function (error, resp) => {} AWS Lambda callback.

Stores the certificate and key in configured S3 bucket. Each file is stored in the certificate or key folder in a file named with reverse domain. For example, if the domain is my.domain.example.com and the S3 bucket is my-certs-bucket, then certificate content will be in s3:///my-certs-bucket/certificate/com.example.domain.my and key content will be in s3:///my-certs-bucket/key/com.example.domain.my.

Errors

BadRequest

Inbound request message does not match schema.

ServiceUnavailable

The certificate recipient is unavailable, please try again soon.

Releases

Policy

We follow the semantic versioning policy (semver.org) with a caveat:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.

caveat: Major version zero is a special case indicating development version that may make incompatible API changes without incrementing MAJOR version.