Rule: prefer N/crypto over Math.random for tokens and secrets

Open
  • Is something wrong?
#56 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start by reading docs/rule-priority.md, then check the SuiteScript type definitions and Oracle documentation to confirm the recommended N/crypto APIs and their replacement forms. Decide how to detect risky Math.random usage, including false positives around @NScriptType, and whether the rule should offer a fix. The issue is done when the rule's detection, severity, preset placement, and fix behavior are settled and implemented.

Written by the indexing model from the issue text.

Description

enhancement needs-triage

TODO: add a rule that prefers N/crypto (and N/crypto/random) over Math.random when generating tokens, IDs or secrets.

Open questions for triage:

  • Confirm against the type definitions and Oracle docs (docs/rule-priority.md tiers) that this is preferable and what the exact replacement APIs are.
  • Detection approach and false-positive risks (e.g. script type via @NScriptType).
  • Whether to offer a fix.
  • Default severity and preset placement.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
2h 8m
Merged PRs (30d)
64

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nemchik/biome-plugin-suitescript

All issues in nemchik/biome-plugin-suitescript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.