Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create 2021-09-08-deprecation.md #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create 2021-09-08-deprecation.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions content/posts/2021-09-08-deprecation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: "Deprecation of this blog"
date: 2021-09-08T11:31:15-05:00
draft: false
---

This blog is inactive and will be removed in 2022.

If you are looking for ways to scan R packages for vulnerabilities, you may find the [oysteR package](https://www.jumpingrivers.com/blog/r-package-vulnerabilities-security/) interesting.

For more information on R package security at RStudio, please see [RStudio's support article](https://support.rstudio.com/hc/en-us/articles/360042593974-R-and-R-Package-Security).

TODO: in the event of a malicious package, how would the RSPM team notify customers? How would a package removal be handled?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think going through support is the most sane option here, that way we can escalate it to Rick and figure out a plan of action