All @algolia/logger-console versions

@algolia/[email protected] rejected Risk: 60 No license

@algolia/logger-console @4.26.0

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
npm Repository Tarball
60
Risk Score
—
License
No
Install Scripts
1
Dependencies
0
Dev Dependencies
.9 KB
Package Size
Published

Maintainers

haroenvshortcutsfluf

Dependencies (1)

PackageConstraintRegistry Status
@algolia/logger-common 4.26.0 auto_approved

Transitive Dependency Tree

1 transitive deps max depth 1
  ├─ @algolia/logger-common 4.26.0 → 4.26.0

Changes from v5.48.1

Dependency Changes

ChangePackageVersion
added @algolia/logger-common 4.26.0
removed @algolia/client-common 5.48.1

Script Changes

- test- build- clean- test:bundle

File Changes

3 added 8 removed 2 modified size delta: -5.3 KB

Risk Dispositions (1 applicable to this version, 0 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
regressed-provenance provenance reject AI AI (provenance): Loss of provenance attestation on a package that previously had it is a strong supply-chain compromise indicator; this judgment generalizes across versions published without attestation.

SAST Findings (3)

HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fluf.

INFO Publisher changed: GitHub Actions → fluf (on 2026-02-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.

Review Summary

Risk score: 60. Findings: 2 high (+50), 1 medium (+10), 2 info (+0).

Published to npm: