Package Health Score

45 / 100

security
Security review needed
popularity
Limited
maintenance
Inactive
community
Sustainable

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
3.6.2	\|	05/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.5.5	\|	07/2018		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.5.3	\|	02/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.2.0	\|	11/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.12	\|	11/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

BSD-3-Clause

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

Limited

Weekly Downloads (337)

GitHub Stars: 1.6K
Forks: 145
Contributors: 30

Direct Usage Popularity

The npm package catalog receives a total of 337 downloads a week. As such, we scored catalog popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package catalog, we found that it has been starred 1,600 times.

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

Community

Sustainable

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

With more than 10 contributors for the catalog repository, this is possibly a sign for a growing and inviting community.

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

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 77
Open PR: 38
Last Release: 4 years ago
Last Commit: 4 years ago

Further analysis of the maintenance status of catalog 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 catalog 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: 11 years
Dependencies: 46 Direct
Versions: 146
Install Size: 3.6 MB
Dist-tags: 3
# of Files: 41
Maintainers: 2
TS Typings: Yes

catalog 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 catalog?

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

cloudera / hue / desktop / core / src / desktop / js / catalog / dataCatalogEntry.js View on Github

getSample(options) {
    const self = this;

    // This prevents caching of any non-standard sample queries, i.e. DISTINCT etc.
    if (options && options.operation && options.operation !== 'default') {
      return catalogUtils.applyCancellable(
        apiHelper.fetchSample({
          sourceType: self.dataCatalog.sourceType,
          compute: self.compute,
          path: self.path,
          silenceErrors: options && options.silenceErrors,
          operation: options.operation
        }),
        options
      );
    }

    // Check if parent has a sample that we can reuse
    if (!self.samplePromise && self.isColumn()) {
      const deferred = $.Deferred();
      const cancellablePromises = [];

View more ways to use catalog

Catalog Logo

Catalog

Catalog lets you create beautiful living and fully interactive style guides using Markdown and React components.

Please read the Catalog documentation (built with Catalog!) for detailed installation and usage instructions.

Installation

yarn

yarn add catalog react react-dom

npm

npm install catalog react react-dom --save

Development

Please make sure that you have Node >= 6 and yarn installed.

Build process

Start the build process in watch mode:

make

Docs

To edit Catalog documentation, run:

make docs

Note: this uses the local Catalog build from dist/. Run make before/alongside make docs.

Linking

When developing Catalog you want to link it locally:

yarn link

You can then link to this version in your project (or one of the examples):

yarn link catalog

Tests

To run Jest tests in watch mode:

make test-watch

Creating a Release

Bump Catalog's version:

make version

Then push including tags:

git push && git push --tags

The CI server will automatically run tests, build and publish the new version to npm

CI commands

These usually run automatically on the CI server

Create a build

make build

Create a documentation build

make build-docs

Publish to npm and generate GitHub release notes

make publish

Credits

Catalog is developed by many people at Interactive Things, a User Experience and Data Visualization Studio based in Zürich.

FAQs

What is catalog?

Create living style guides using Markdown or React. Visit Snyk Advisor to see a full health score report for catalog, including popularity, security, maintenance & community analysis.

Is catalog popular?

The npm package catalog receives a total of 337 weekly downloads. As such, catalog popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is catalog well maintained?

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

Is catalog safe to use?

While scanning the latest version of catalog, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 21 December-2024, at 15:40 (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