Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
The script can be use :
The supported system are :
At the first run, you will be asked to configure some key and specific path.
share
key. By default, it's share
(i)
docs/notes
but you can change that, or use /
for root.Global options :
--git
: No commit and push to git ;--mobile
: Use mobile shortcuts instead of --git
--meta
: Update frontmatter of source files--keep
: Don't delete files in blog folder--shell
: Remove Rich printingCommands and specific options :
--use configuration_name
)
--new configuration_name
: Create a specific configuration for some files--force
: Force updating (ignore the difference between the source and blog file)--vault
: Share all vault file, ignoring the share state.file [file]
: Share only one fileusage: __main__.py [-h] [--mobile | --git] [--meta] [--keep] [--use configuration_name] {config,all,file} ...
positional arguments:
{config,all,file}
config Configure the script : Add or edit your vault and blog absolute path, change some keys.
all Publish multiple files
file Publish only one file
options:
-h, --help show this help message and exit
--mobile, --shortcuts
Use mobile shortcuts, without push
--git, --g, --G No commit and no push to git
--meta, --m, --M Update the frontmatter of the source file, adding the note blog's link
--keep, --k, --K Keep deleted file from vault and removed shared file
--use configuration_name, --config configuration_name
Use a different config from default
The commands order is :
obs2mk (global_options) [all|config|file FILEPATH] (specific_options)
Where :
all
, config
and file
1 are required
You can use the command without argument with obs2mk
to share every share: true
file in your vault.obs2mk file FILEPATH
It will :
share
state in original fileshare
state.obs2mk all
or obs2mk
You can share multiple documents at once with scanning your Vault, looking for the share: true
. It will convert automatically these files.
Only file with modification since the last sharing will be updated.
You can :
share
state) with : obs2mk all --vault
obs2mk all --force
Also, you can combine the two options.You can use and create multiple configuration files. This allows to have multiple site based on one vault, or different vault accross one site...
obs2mk config --new configuration_name
--use configuration_name
For example : obs2mk --use configuration_name
See [[configuration template]] for more information about the configuration file.
For file
you need to add the filepath of the file you want to share : obs2mk (global_option) file "filepath" (specific_options)
↩
FAQs
A script to share your obsidian vault (in partial way) using mkdocs
We found that obs2mk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.