Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add lockfile validation

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js
Domain
security, tooling

Research direction

No repository files or tests are named. Start by reviewing how the Git repositories are configured and the lockfile-lint project, focusing on its support for NPM and Yarn lockfiles and permitted hosts and URL schemes. Done means lockfile-lint is added to the relevant repositories with validation enabled.

Written by the indexing model from the issue text.

Description

Lockfiles are generally treated as an opaque format, and as such are typically ignored during code review. However, they can be an attack vector if they are modified to download malicious packages instead. This is because lockfiles only check for integrity but not authenticity.

lockfile-lint is a project maintained by a Snyk staff which can notably enforce the permitted hosts and URL schemes within NPM and Yarn lockfiles.

This issue is to track adding of lockfile-lint to our Git Repositories.

Dominant language
TypeScript
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/security

All issues in loopbackio/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.