Security News
Opengrep Emerges as Open Source Alternative Amid Semgrep Licensing Controversy
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
work in progress
the future is bright
npm install bright
Use it from a server component, for example in Next.js app/page.js
:
import { Code } from "bright"
export default function Page() {
return <Code lang="py">print("hello brightness")</Code>
}
import { Code } from "bright"
const myCode = `
let hello = "hello brightness"
console.log(hello, "my old friend")
`.trim()
export default function Page() {
return (
<Code lang="js" lineNumbers>
{myCode}
</Code>
)
}
import { Code } from "bright"
const myCode = `
let hello = "hello brightness"
console.log(hello, "my old friend")
`.trim()
// you can set any prop globally
Code.lineNumbers = true
export default function Page() {
return <Code lang="js">{myCode}</Code>
}
import { Code } from "bright"
// there are some built in themes
// typescript should autocomplete this
Code.theme = "github-dark"
export default function Page() {
return <Code lang="py">print("hello brightness")</Code>
}
FAQs
> the future is bright
The npm package bright receives a total of 2,447 weekly downloads. As such, bright popularity was classified as popular.
We found that bright demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.