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.
@flycode-org/netlify-plugin-flycode
Advanced tools
Netlify Build plugin - Inject FlyCode SDK to start editing your app
In order to use this plugin, install it as a dependency to your project using
npm install --save @flycode/netlify-plugin
or
yarn add @flycode/netlify-plugin
Next (and last) step is to use this plugin in Netlify config file.
If you don't have such file, create netlify.toml
file in your project's root directory with contents:
[[plugins]]
package = "@flycode-org/netlify-plugin-flycode"
If netlify.toml
already exists in your project, add the code above at the end of that file, to achieve similar result:
[[plugins]]
package = "..."
[[plugins]]
package = "..."
[[plugins]]
package = "@flycode-org/netlify-plugin-flycode"
Make sure to commit changes made to this file and either merge these to the main branch through a Pull Request or push directly.
In your next Netlify deploy you should see the plugin in action.
Instead of configuring the plugin to be used in every deploy, you can configure it to be executed only in certain cases.
The case we focus on is Deploy Preview, so if you want to avoid running this plugin on production deploy (see below why it's not a big deal), you might want to add this to the netlify.toml
instead:
[[context.deploy-preview.plugins]]
package = "@flycode-org/netlify-plugin-flycode"
[[plugins]]
is no big dealOur plugin will proceed with its job only if it detects the current context is Deploy Preview. This means that when it's a Production deploy, you will most likely see a message:
Not a deploy preview. Skipping...
And that will conclude our plugin's life.
Debugging allows you to view during its execution a stringified data that is used in the plugin. This includes:
For debugging options, you can specify a debug mode as shown below:
[[plugins]]
package = "@flycode-org/netlify-plugin-flycode"
[plugins.inputs]
debug = true
For the deploy-preview context:
[[context.deploy-preview.plugins]]
package = "@flycode-org/netlify-plugin-flycode"
[context.deploy-preview.plugins.inputs]
debug = true
FAQs
Netlify Build plugin - Inject FlyCode SDK to start editing your app
The npm package @flycode-org/netlify-plugin-flycode receives a total of 2 weekly downloads. As such, @flycode-org/netlify-plugin-flycode popularity was classified as not popular.
We found that @flycode-org/netlify-plugin-flycode demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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.