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.
Speech (Voice) Module for Neon Core. This module can be treated as a replacement for the mycroft-core speech module. This module handles input audio, performs STT, and optionally returns the text or forwards it to the skills module for intent parsing.
neon-speech
extends mycroft-speech
with the following added functionality:
Mycroft STT and Wake Word plugins are compatible with neon-speech
, with the exception of skipping wake words,
which is currently only supported by Neon STT plugins.
The included Dockerfile
may be used to build a docker container for the neon_speech module. The below command may be used
to start the container.
docker run -d \
--network=host \
--name=neon_speech \
-v ~/.config/pulse/cookie:/tmp/pulse_cookie:ro \
-v ${XDG_RUNTIME_DIR}/pulse:${XDG_RUNTIME_DIR}/pulse:ro \
--device=/dev/snd:/dev/snd \
-e PULSE_SERVER=unix:${XDG_RUNTIME_DIR}/pulse/native \
-e PULSE_COOKIE=/tmp/pulse_cookie \
neon_speech
FAQs
Neon Speech Module
We found that neon-speech demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers 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.