diff --git a/.gitignore b/.gitignore
index 19ce3a56..4e2adb90 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
+.env
 /codegen/target
 /target
 node_modules
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 07c00250..067bf266 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,11 @@ Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
 
 #### [Unreleased](https://github.com/hougesen/mdsf/compare/v0.4.1...HEAD)
 
+- chore(vscode): add metadata keys to package.json [`#670`](https://github.com/hougesen/mdsf/pull/670)
+- build(deps-dev): bump @typescript-eslint/parser in /mdsf-vscode [`#669`](https://github.com/hougesen/mdsf/pull/669)
+- build(deps-dev): bump @typescript-eslint/eslint-plugin in /mdsf-vscode [`#668`](https://github.com/hougesen/mdsf/pull/668)
+- build(deps): bump toml from 0.8.19 to 0.8.20 [`#666`](https://github.com/hougesen/mdsf/pull/666)
+- build(deps): bump clap from 4.5.27 to 4.5.28 [`#665`](https://github.com/hougesen/mdsf/pull/665)
 - feat: add support for coffeelint [`#664`](https://github.com/hougesen/mdsf/pull/664)
 - build(deps): bump tempfile from 3.15.0 to 3.16.0 [`#659`](https://github.com/hougesen/mdsf/pull/659)
 - build(deps): bump clap_complete from 4.5.43 to 4.5.44 [`#660`](https://github.com/hougesen/mdsf/pull/660)
diff --git a/mdsf-vscode/CHANGELOG.md b/mdsf-vscode/CHANGELOG.md
deleted file mode 100644
index b69d8de6..00000000
--- a/mdsf-vscode/CHANGELOG.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Change Log
-
-All notable changes to the "mdsf-vscode" extension will be documented in this file.
-
-Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
-
-## [Unreleased]
-
-- Initial release
diff --git a/mdsf-vscode/package.json b/mdsf-vscode/package.json
index e618ff5e..22150ca4 100644
--- a/mdsf-vscode/package.json
+++ b/mdsf-vscode/package.json
@@ -1,6 +1,7 @@
 {
   "name": "mdsf-vscode",
   "displayName": "mdsf",
+  "publisher": "hougesen",
   "description": "Format markdown code blocks using mdsf",
   "version": "0.0.1",
   "engines": {
@@ -23,6 +24,35 @@
       }
     ]
   },
+  "languages": [
+    {
+      "id": "ignore",
+      "extensions": [
+        ".mdsfignore"
+      ]
+    }
+  ],
+  "homepage": "https://github.com/hougesen/mdsf",
+  "author": {
+    "email": "mads@mhouge.dk",
+    "name": "Mads Hougesen",
+    "url": "https://mhouge.dk"
+  },
+  "license": "MIT",
+  "keywords": [
+    "formatter",
+    "linter",
+    "markdown",
+    "mdsf"
+  ],
+  "bugs": {
+    "url": "https://github.com/hougesen/mdsf/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/hougesen/mdsf.git",
+    "directory": "mdsf-vscode"
+  },
   "scripts": {
     "vscode:prepublish": "pnpm run package",
     "compile": "pnpm run check-types && pnpm run lint && node esbuild.js",
diff --git a/mdsf-vscode/vsc-extension-quickstart.md b/mdsf-vscode/vsc-extension-quickstart.md
deleted file mode 100644
index e2d793c2..00000000
--- a/mdsf-vscode/vsc-extension-quickstart.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# Welcome to your VS Code Extension
-
-## What's in the folder
-
-- This folder contains all of the files necessary for your extension.
-- `package.json` - this is the manifest file in which you declare your extension and command.
-  - The sample plugin registers a command and defines its title and command name. With this information VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
-- `src/extension.ts` - this is the main file where you will provide the implementation of your command.
-  - The file exports one function, `activate`, which is called the very first time your extension is activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
-  - We pass the function containing the implementation of the command as the second parameter to `registerCommand`.
-
-## Setup
-
-- install the recommended extensions (amodio.tsl-problem-matcher, ms-vscode.extension-test-runner, and dbaeumer.vscode-eslint)
-
-## Get up and running straight away
-
-- Press `F5` to open a new window with your extension loaded.
-- Run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`.
-- Set breakpoints in your code inside `src/extension.ts` to debug your extension.
-- Find output from your extension in the debug console.
-
-## Make changes
-
-- You can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`.
-- You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes.
-
-## Explore the API
-
-- You can open the full set of our API when you open the file `node_modules/@types/vscode/index.d.ts`.
-
-## Run tests
-
-- Install the [Extension Test Runner](https://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
-- Run the "watch" task via the **Tasks: Run Task** command. Make sure this is running, or tests might not be discovered.
-- Open the Testing view from the activity bar and click the Run Test" button, or use the hotkey `Ctrl/Cmd + ; A`
-- See the output of the test result in the Test Results view.
-- Make changes to `src/test/extension.test.ts` or create new test files inside the `test` folder.
-  - The provided test runner will only consider files matching the name pattern `**.test.ts`.
-  - You can create folders inside the `test` folder to structure your tests any way you want.
-
-## Go further
-
-- Reduce the extension size and improve the startup time by [bundling your extension](https://code.visualstudio.com/api/working-with-extensions/bundling-extension).
-- [Publish your extension](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) on the VS Code extension marketplace.
-- Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).