# Gemnasium and CircleCI - GEMNASIUM\_TOKEN seems to not get picked up

**URL:** <https://discuss.circleci.com/t/gemnasium-and-circleci-gemnasium-token-seems-to-not-get-picked-up/12294>\
**Category:** Build Environment\
**Tags:** ruby, envars, circle-yml\
**Created:** [April 30, 2017, 7:30pm UTC](https://discuss.circleci.com/t/gemnasium-and-circleci-gemnasium-token-seems-to-not-get-picked-up/12294 "2017-04-30T19:30:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [May 2, 2017, 6:06am UTC](https://discuss.circleci.com/t/gemnasium-and-circleci-gemnasium-token-seems-to-not-get-picked-up/12294/2 "2017-05-02T06:06:45Z")

</div>

If you take a look at the build output you will see this:

```auto
Suppressing export of environment variables DOCKEREMAIL, DOCKERLOGIN, DOCKERPASS, BRAKEMAN_PRO_URL, GEMNASIUM_TESTSUITE, GEMNASIUM_PROJECT_SLUG, GEMNASIUM_TOKEN fork PR builds

```

On Fork PR builds we do not export ENVARS since this would mean that anyone who opens a fork will be able to see your secrets (i.e. by adding `echo $ENVAR` to circle.yml)

You can enable ENVARS for forks in project settings, but we do not recommend doing this.

---

_[View the full topic](https://discuss.circleci.com/t/gemnasium-and-circleci-gemnasium-token-seems-to-not-get-picked-up/12294)._