Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
github.com/joshuatcasey/bundler
gcr.io/paketo-buildpacks/bundler
The Bundler CNB provides the Bundler binary. The buildpack installs the Bundler
onto the $PATH
and $GEM_PATH
which makes it available for subsequent buildpacks
and in the final running container.
The Bundler CNB provides bundler as a dependency. Downstream buildpacks, can require the bundler dependency by generating a Build Plan TOML file that looks like the following:
[[requires]]
# The name of the Bundler dependency is "bundler". This value is considered
# part of the public API for the buildpack and will not change without a plan
# for deprecation.
name = "bundler"
# The version of the Bundler dependency is not required. In the case it
# is not specified, the buildpack will provide the default version, which can
# be seen in the buildpack.toml file.
# If you wish to request a specific version, the buildpack supports
# specifying a semver constraint in the form of "2.*", "2.1.*", or even
# "2.1.4".
version = "2.1.4"
# The Bundler buildpack supports some non-required metadata options.
[requires.metadata]
# Setting the build flag to true will ensure that the Bundler
# depdendency is available on the $PATH for subsequent buildpacks during
# their build phase. If you are writing a buildpack that needs to run Bundle
# during its build process, this flag should be set to true.
build = true
To package this buildpack for consumption:
$ ./scripts/package.sh
This builds the buildpack's Go source using GOOS=linux by default. You can supply another value as the first argument to package.sh.
Specifying the Bundler
version through buildpack.yml
configuration will be
deprecated in Bundler Buildpack v1.0.0.
To migrate from using buildpack.yml
please set the $BP_BUNDLER_VERSION
environment variable at build time either directly (ex. pack build my-app --env BP_BUNDLER_VERSION=2.7.*
) or through a project.toml
file
$BP_BUNDLER_VERSION="2.1.4"
This will replace the following structure in buildpack.yml
:
bundler:
version: 2.1.4
To configure the level of log output from the buildpack itself, set the
$BP_LOG_LEVEL
environment variable at build time either directly (ex. pack build my-app --env BP_LOG_LEVEL=DEBUG
) or through a project.toml
file
If no value is set, the default value of INFO
will be used.
The options for this setting are:
INFO
: (Default) log information about the progress of the build processDEBUG
: log debugging information about the progress of the build process$BP_LOG_LEVEL="DEBUG"
FAQs
Unknown package
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
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.