Gathering detailed insights and metrics for sequelize-mig
Gathering detailed insights and metrics for sequelize-mig
Gathering detailed insights and metrics for sequelize-mig
Gathering detailed insights and metrics for sequelize-mig
Sequelize migration generator and es6 init tool (Planned)
npm install sequelize-mig
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
67 Stars
1,369 Commits
14 Forks
1 Watchers
32 Branches
18 Contributors
Updated on Nov 25, 2024
Latest Version
3.1.3
Package Id
sequelize-mig@3.1.3
Unpacked Size
59.51 kB
Size
17.81 kB
File Count
17
NPM Version
6.14.8
Node Version
14.13.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
20
1Warning: THIS TOOL IS UNDER DEVELOPMENT AND NOT INTENDED TO PRODUCTION USE RIGHT NOW!!!!
The tool is built using es6 And its not intended to replace sequelize-cli its just completing it
This tool provide these commands:
migration:make
or migration:add
- to create new migrations by comparing new version of your modules to old onesmigration:undo
or migration:revert
- delete last migration file and return to backup state file of the modelsmigration:sync
- Sync the models schema file with current models without migrating (Planned)Planned:
init
- tool to init required files for sequelize using new es6 schema (Planned)(Globally - Recommended)
1npm install sequelize-mig -g / yarn global add sequelize-mig
Or
(devDependencies)
1npm install sequelize-mig -D / yarn add sequelize-mig -D
sequelize init
(or using es6 init by sequelize-mig -Planned-)1sequelize-mig migration:make -n <migration name>
1sequelize-mig migration:make --preview
sequelize db:migrate
If you already used migrations before knowing this tool you can easily fully migrate in the sequelize-cli tool
and then run migration:sync
and tool will update _current.json
and you can continue using this tool normally
The migration:make tool supports auto detecting these actions
1dropTable, removeColumn, removeIndex, 2createTable, addColumn, addIndex, 3changeColumn
and Im trying to find a way to know old column name to implement renameColumn because it's now translated to removeColumn then addColumn
The tool works by getting the schema of the models into _current.json
and every time you run migration:make
the tool will compare this file with new schema and write the new migration file
then this tool cant actually know if you deleted, or migrated or whatever you edited to these files...
migration:make
tool creates _current.json
and _current_bak.json
files in migrations
dir, these are used to calculate difference to the next migration. Do not remove them!{timestamp}_{name}.{js|cjs}
but you can change every single option with parametersrenameColumn
in some way I didn't know until now (maybe comments)No vulnerabilities found.
Reason
all changesets reviewed
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
security policy file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
70 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More