I'm opening this issue because:

• npm is producing an incorrect install.

What's going wrong?

• npm pack with 5.7.1 on node 8.9.4 is setting bogus epoch file timestamps.
• This is not an issue in 5.6.0.
• These old timestamps are apparently a problem for some zip programs.
• This was brought to my attention via researching the cause of node-forge: Unhandled exception - ZIP does not support timestamps before 1980 digitalbazaar/forge#568
• Looks similar to a previous issue: npm5 beta 56: npm pack changes timestamps to 01/01/1970 on Windows 7 #16734
• I've been publishing packages with these bogus timestamps since upgrading to 5.7.1. Based on grabbing some random recent tarballs from npm homepage it looks like other people are publishing packages with the same timestamp issue.

How can the CLI team reproduce the problem?

• Pick a project, any project:
• npm pack
• tar ztvf xxx-x.y.z.tgz

-rw-rw-r-- 0/0            3487 1969-12-31 19:00 package/package.json
-rw-rw-r-- 0/0            4801 1969-12-31 19:00 package/CHANGELOG.md
...

Timestamps for all files are like new Date(0) with display adjusted for my timezone.

supporting information:

• npm -v prints: 5.7.1
• node -v prints: v8.9.4
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Linux (Debian latest)