View tiny-decoders on Snyk Open Source Advisor

Package Health Score

58 / 100

security
No known security issues
popularity
Small
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

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
20.1.0	\|	10/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
21.0.0	\|	10/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
22.0.0	\|	10/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
23.0.0	\|	10/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
20.0.0	\|	10/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

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 (6,808)

GitHub Stars: 52
Forks: 1
Contributors: 2

Direct Usage Popularity

The npm package tiny-decoders receives a total of 6,808 downloads a week. As such, we scored tiny-decoders popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package tiny-decoders, we found that it has been starred 52 times.

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

Community

Limited

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

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like tiny-decoders is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 1 year ago
Last Commit: 2 months ago

Further analysis of the maintenance status of tiny-decoders based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for tiny-decoders is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

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: 6 years
Dependencies: 0 Direct
Versions: 31
Install Size: 67 kB
Dist-tags: 1
# of Files: 6
Maintainers: 1
TS Typings: No

tiny-decoders 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.

Not sure how to use tiny-decoders?

To help you get started, we've collected the most common ways that tiny-decoders is being used within popular public projects.

lydell / tiny-decoders / typescript / type-annotations.ts View on Github

return `${personA.name} meets ${personB.name}`;
}
meet(personDecoder9(testPerson), personDecoder9Auto(testPerson));

// If it feels like you are specifying everything twice – once in a `type` or
// `interface`, and once in the decoder – you might find this `ReturnType`
// technique interesting. If annotating your decoders like shown earlier in this
// file (`record((field): MyType =&gt; ({...}))` and `autoRecord({...})`),
// TypeScript will make sure that your type definition and decoders stay in
// sync, so there’s little room for error there. But with the `ReturnType`
// approach you don’t have to write what your records look like “twice.”
// Personally I don’t mind the “duplication,” but if you do – try out the
// `ReturnType` approach!

// Here’s a more complex example for trying out TypeScript’s inference.
const userDecoder = autoRecord({
  id: either(string, number),
  name: string,
  age: number,
  active: boolean,
  country: optional(string),
  type: constant("user"),
});

// Let TypeScript infer the `User` type:
type User = ReturnType;
// Try hovering over `User` in the line above – your editor should reveal the
// exact shape of the type.

const data = {
  id: 1,
  name: "John Doe",

View more ways to use tiny-decoders

FAQs

What is tiny-decoders?

Type-safe data decoding for the minimalist. Visit Snyk Advisor to see a full health score report for tiny-decoders, including popularity, security, maintenance & community analysis.

Is tiny-decoders popular?

The npm package tiny-decoders receives a total of 6,808 weekly downloads. As such, tiny-decoders popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is tiny-decoders well maintained?

We found indications that tiny-decoders is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is tiny-decoders safe to use?

The npm package tiny-decoders was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 7 November-2024, at 13:32 (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

tiny-decoders

Type-safe data decoding for the minimalist. For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (6,808)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use tiny-decoders?

tiny-decoders

FAQs

What is tiny-decoders?

Is tiny-decoders popular?

Is tiny-decoders well maintained?

Is tiny-decoders safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (6,808)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use tiny-decoders?

tiny-decoders

FAQs

What is tiny-decoders?

Is tiny-decoders popular?

Is tiny-decoders well maintained?

Is tiny-decoders safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues