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.
strapi-plugin-content-type-builder
Advanced tools
Hello! We have some news to share,
We’ve decided it’ll soon be time to end the support for strapi-plugin-content-type-builder
.
After years of iterations, Strapi is going to V4 and we won’t maintain V3 packages when it’ll reach its end-of-support milestone (~end of Q3 2022).
If you’ve been using strapi-plugin-content-type-builder
and have migrated to V4 (or if you want to), you can find the equivalent and updated version of this package at this URL and with the following name on NPM: @strapi/plugin-content-type-builder
.
If you’ve contributed to the development of this package, thank you again for that! We hope to see you on the V4 soon.
The Strapi team
FAQs
Strapi plugin to create content type (API).
The npm package strapi-plugin-content-type-builder receives a total of 30,623 weekly downloads. As such, strapi-plugin-content-type-builder popularity was classified as popular.
We found that strapi-plugin-content-type-builder demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 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.