-
-
Notifications
You must be signed in to change notification settings - Fork 216
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: isaacs/node-tar
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.5.7
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: isaacs/node-tar
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.5.10
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 10 files changed
- 2 contributors
Commits on Feb 13, 2026
-
fix: do not write linkpaths through symlinks
Prevent any `Link` or `SymbolicLink` entry from being created if its `linkpath` would target a location that is through a symbolic link from the current working directory. This matches the behavior of `bsdtar` for hard links, and is somewhat more restrictive in applying the same logic to symbolic links as well. Unpacking links with targets that extend through symlink folders is allowed if `preservePaths` option is enabled, as this disables all protective link checking by design, and is only designed for use with trusted input. Fix: GHSA-83g3-92jg-28cx
Configuration menu - View commit details
-
Copy full SHA for d18e4e1 - Browse repository at this point
Copy the full SHA d18e4e1View commit details
Commits on Feb 16, 2026
-
fix(unpack): improve UnpackSync symlink error "into" path accuracy
UnpackSync[ENSURE_NO_SYMLINK] previously constructed SymlinkError's "into" path using the full original linkpath parts array, which could produce misleading diagnostics. Build the "into" path from the original `cwd` value and the `parts` list.
Configuration menu - View commit details
-
Copy full SHA for 2cb1120 - Browse repository at this point
Copy the full SHA 2cb1120View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6b8eba0 - Browse repository at this point
Copy the full SHA 6b8eba0View commit details -
Configuration menu - View commit details
-
Copy full SHA for fbb0851 - Browse repository at this point
Copy the full SHA fbb0851View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1f0c2c9 - Browse repository at this point
Copy the full SHA 1f0c2c9View commit details
Commits on Mar 4, 2026
-
Configuration menu - View commit details
-
Copy full SHA for c8cb846 - Browse repository at this point
Copy the full SHA c8cb846View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7bc755d - Browse repository at this point
Copy the full SHA 7bc755dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2b72abc - Browse repository at this point
Copy the full SHA 2b72abcView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v7.5.7...v7.5.10