
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
@codecov/astro-plugin
Advanced tools
An Astro integration that provides bundle analysis support for Codecov.
[!NOTE] The plugin does not support code coverage, see our docs to set up coverage today!
Using npm:
npx astro add @codecov/astro-plugin
Using yarn:
yarn astro add @codecov/astro-plugin
Using pnpm:
pnpm astro add @codecov/astro-plugin
This configuration will automatically upload the bundle analysis to Codecov for public repositories. When an internal PR is created it will use the Codecov token set in your secrets, and if running from a forked PR, it will use the tokenless setting automatically. For setups not using GitHub Actions see the following example. For private repositories see the following example.
// astro.config.mjs
import { defineConfig } from "astro/config";
import { codecovAstroPlugin } from "@codecov/astro-plugin";
// https://astro.build/config
export default defineConfig({
// other config settings
integrations: [
// place this after all other integrations
codecovAstroPlugin({
enableBundleAnalysis: true,
bundleName: "example-astro-bundle",
uploadToken: process.env.CODECOV_TOKEN,
gitService: "github",
}),
],
});
This setup is for public repositories that are not using GitHub Actions, this configuration will automatically upload the bundle analysis to Codecov. You will need to configure the it similar to the GitHub Actions example, however you will need to provide a branch override, and ensure that it will pass the correct branch name, and with forks including the fork-owner i.e. fork-owner:branch
.
// astro.config.mjs
import { defineConfig } from "astro/config";
import { codecovAstroPlugin } from "@codecov/astro-plugin";
// https://astro.build/config
export default defineConfig({
// other config settings
integrations: [
// place this after all other integrations
codecovAstroPlugin({
enableBundleAnalysis: true,
bundleName: "example-astro-bundle",
uploadToken: process.env.CODECOV_TOKEN,
gitService: "github",
uploadOverrides: {
branch: "<branch value>",
},
}),
],
});
This is the required way to use the plugin for private repositories. This configuration will automatically upload the bundle analysis to Codecov.
This configuration will automatically upload the bundle analysis to Codecov for public repositories. When an internal PR is created it will use the Codecov token set in your secrets, and if running from a forked PR, it will use the tokenless setting automatically. For setups not using GitHub Actions see the following example. For private repositories see the following example.
// astro.config.mjs
import { defineConfig } from "astro/config";
import { codecovAstroPlugin } from "@codecov/astro-plugin";
// https://astro.build/config
export default defineConfig({
// other config settings
integrations: [
// place this after all other integrations
codecovAstroPlugin({
enableBundleAnalysis: true,
bundleName: "example-astro-bundle",
uploadToken: process.env.CODECOV_TOKEN,
}),
],
});
For users with OpenID Connect (OIDC) enabled, setting the uploadToken
is not necessary. You can use OIDC with the oidc
configuration as following.
// astro.config.mjs
import { defineConfig } from "astro/config";
import { codecovAstroPlugin } from "@codecov/astro-plugin";
// https://astro.build/config
export default defineConfig({
// other config settings
integrations: [
// place this after all other integrations
codecovAstroPlugin({
enableBundleAnalysis: true,
bundleName: "example-astro-bundle",
oidc: {
useGitHubOIDC: true,
},
}),
],
});
FAQs
Official Codecov Astro Plugin
We found that @codecov/astro-plugin demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 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.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.