package-time-traveler

v3.0.1

Simulate an npm install on a specific day (for better re-use of npm packages preadating package-lock.json) For more information about how to use this package see README

Latest version published 6 months ago

License: ISC

NPM

GitHub

Package Health Score

63 / 100

security
No known security issues
popularity
Limited
maintenance
Sustainable
community
Limited

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version			Vulnerabilities	License Risk
3.0.1	\|	07/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.2	\|	03/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.0	\|	02/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.0	\|	02/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

ISC

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (1)

GitHub Stars: 6
Forks: 2
Contributors: 3

Direct Usage Popularity

The npm package package-time-traveler receives a total of 1 downloads a week. As such, we scored package-time-traveler popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package package-time-traveler, we found that it has been starred 6 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 3
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like package-time-traveler is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 0
Open PR: 4
Last Release: 6 months ago
Last Commit: 2 months ago

Further analysis of the maintenance status of package-time-traveler based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that package-time-traveler demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 5 years
Dependencies: 2 Direct
Versions: 7
Install Size: 5.28 kB
Dist-tags: 1
# of Files: 4
Maintainers: 1
TS Typings: No

package-time-traveler has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

package-time-traveler

package-time-traveler tells you what npm i would do for a given package.json file on any given date. It does this by adhering to the existing package.json's package version specs while restricting the package to versions published before a given date.

This might be useful if you have an old package that predates package-lock.json, and that package has misbehaved dependencies that don't respect semver. package-time-traveler can help you simulate what dependencies the original author would have been using.

Usage

package-time-traveler /path/to/package.json DATE

Example

If you'd like to replicate what npm i would have done on 2018-07-31 for the termux-appium package, you would:

npm i -g package-time-traveler
git clone git@github.com:goodguysoftware/termux-appium.git
package-time-traveler termux-appium/package.json 2018-07-31

{
  "dependencies": {
    "adbkit": "2.11.0",
    "appium-adb": "6.14.0",
    "appium-android-driver": "3.3.0",
    "appium-base-driver": "3.4.0",
    "appium-support": "2.20.0",
    "appium-uiautomator2-server": "1.13.0",
    "asyncbox": "2.4.0",
    "babel-runtime": "5.8.24",
    "bluebird": "3.5.1",
    "lodash": "4.17.10",
    "portscanner": "2.2.0",
    "request": "2.87.0",
    "request-promise": "4.2.2",
    "source-map-support": "0.5.6",
    "teen_process": "1.13.0",
    "utf7": "1.0.2",
    "ws": "6.0.0"
  },
  "devDependencies": {
    "android-apidemos": "3.0.0",
    "appium-gulp-plugins": "2.4.1",
    "appium-test-support": "1.0.0",
    "babel-eslint": "7.2.3",
    "chai": "4.1.2",
    "chai-as-promised": "7.1.1",
    "eslint": "3.19.0",
    "eslint-config-appium": "2.1.0",
    "eslint-plugin-babel": "3.3.0",
    "eslint-plugin-import": "2.13.0",
    "eslint-plugin-mocha": "4.12.1",
    "eslint-plugin-promise": "3.8.0",
    "gps-demo-app": "2.1.1",
    "gulp": "3.9.1",
    "pngjs": "3.3.3",
    "pre-commit": "1.2.2",
    "rimraf": "2.6.2",
    "sinon": "6.1.4",
    "unzip": "0.1.11",
    "wd": "1.10.3",
    "xmldom": "0.1.27",
    "xpath": "0.0.27"
  }
}

Replace the dependencies in termux-appium/package.json with the output above and then npm i again.

package-time-traveler dependencies

pacote @altano/tiny-async-pool

FAQs

What is package-time-traveler?

Simulate an npm install on a specific day (for better re-use of npm packages preadating package-lock.json). Visit Snyk Advisor to see a full health score report for package-time-traveler, including popularity, security, maintenance & community analysis.

Is package-time-traveler popular?

The npm package package-time-traveler receives a total of 1 weekly downloads. As such, package-time-traveler popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is package-time-traveler well maintained?

We found indications that package-time-traveler maintenance is sustainable demonstrating some project activity. We saw a total of 3 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is package-time-traveler safe to use?

The npm package package-time-traveler was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 15 December-2024, at 02:29 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (1)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

package-time-traveler

Usage

Example

package-time-traveler dependencies

FAQs

What is package-time-traveler?

Is package-time-traveler popular?

Is package-time-traveler well maintained?

Is package-time-traveler safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues