Package Health

@algolia/monitoring

This release appears healthy and suitable for dependency use: it is actively and frequently released, stable, non-deprecated, licensed, typed, provenance-attested, and backed by a non-archived organization-owned repository with recent activity from 10 contributors. The main reservations are repository transparency—the linked monorepo neither matches the package name nor mentions it in its README—and some security-governance gaps, including no security policy and mixed workflow permission hygiene; recent issue activity is also quiet. These concerns warrant review of the repository and release process but do not outweigh the strong maintenance and provenance evidence.

Latest 1.59.0NPMNPM

88%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

90

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

95

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

70

Attestations
Attestations
Measures the presence and validity of package attestations and signatures

100

Health Score Breakdown

Dangerous workflowscaution

One of three analyzed workflows uses pull_request_target, which warrants review because that trigger can expose privileged workflow execution to pull requests; no untrusted checkout or script-injection patterns were detected to offset the concern.

Repo issue activitycaution

There were no new or closed issues and no merged pull requests in the last month, which is a mild maintenance-visibility concern despite stronger recent commit and release activity.

Repo package mentioncaution

The linked repository does not match the package name and does not mention @algolia/monitoring in its README. Although a name mismatch is ordinary for a monorepo, the lack of a README mention reduces package-to-repository transparency.

Security policycaution

The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting and response expectations undocumented.

Token permissionscaution

Workflow permission hygiene is mixed: one workflow lacks top-level permissions and the release workflow has top-level write permissions, while only one workflow is explicitly read-only. This increases governance risk, although it is not evidence of unsafe behavior by itself.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Direct Dependencies

DependencyLast ReleaseScore
@algolia/client-common
Version 5.59.0
—
—
@algolia/requester-fetch
Version 5.59.0
—
—
@algolia/requester-node-http
Version 5.59.0
—
—
@algolia/requester-browser-xhr
Version 5.59.0
—
—

Weekly Downloads

Info

Last Published
26 days ago
Created
3 years ago
Unpacked Size
0.9 MB

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform