Research
Security News
Malicious npm Package Targets Solana Developers and Hijacks Funds
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Built-in metrics for GraphQL-Ruby monitoring out of the box! Part of the yabeda suite.
Get sample Grafana dashboard from Grafana.com #14774 or from grafana-dashboard.json
file.
Add the gem to your Gemfile:
gem 'yabeda-graphql'
# Then add monitoring system adapter, e.g.:
# gem 'yabeda-prometheus'
# If you're using Rails don't forget to add plugin for it:
# gem 'yabeda-rails'
# But if not then you should run `Yabeda.configure!` manually when your app is ready.
And then execute:
bundle install
Hook it to your schema:
class YourAppSchema < GraphQL::Schema
use Yabeda::GraphQL
end
And deploy it!
And that is it! GraphQL metrics are being collected!
graphql_fields_request_count
(segmented by type
name, field
name and deprecated
flag)graphql_field_resolve_runtime
(segmented by type
name, field
name and deprecated
flag)query_fields_count
(segmented by query name
and deprecated
flag)mutation_fields_count
(segmented by query name
and deprecated
flag)That is it for now, but more will come later.
After checking out the repo, run bin/setup
to install dependencies.
Then, run fololowing commands to run the tests against all supported versions of GraphQL-Ruby:
bundle exec appraisal rspec
You can also run bin/console
for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
. To release a new version, update the version number in version.rb
, and then run bundle exec rake release
, which will create a git tag for the version, push git commits and tags, and push the .gem
file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/yabeda-rb/yabeda-graphql.
Bump version number in lib/yabeda/graphql/version.rb
In case of pre-releases keep in mind rubygems/rubygems#3086 and check version with command like Gem::Version.new(Yabeda::GraphQL::VERSION).to_s
Fill CHANGELOG.md
with missing changes, add header with version and date.
Make a commit:
git add lib/yabeda/graphql/version.rb CHANGELOG.md
version=$(ruby -r ./lib/yabeda/graphql/version.rb -e "puts Gem::Version.new(Yabeda::GraphQL::VERSION)")
git commit --message="${version}: " --edit
Create annotated tag:
git tag v${version} --annotate --message="${version}: " --edit --sign
Fill version name into subject line and (optionally) some description (list of changes will be taken from changelog and appended automatically)
Push it:
git push --follow-tags
GitHub Actions will create a new release, build and push gem into RubyGems! You're done!
The gem is available as open source under the terms of the MIT License.
FAQs
Unknown package
We found that yabeda-graphql demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.