publishConfigRedundancy

Reports publishConfig.access fields that do not affect unscoped packages.

✅ This rule is included in the package-json logical presets.

This rule reports publishConfig.access fields in unscoped packages. Unscoped npm packages are always published with public access, so this field only changes publishing behavior for scoped packages.

Examples

❌ Incorrect

{
  "name": "my-package",
  "publishConfig": {
    "access": "public"
  }
}

{
  "name": "my-package",
  "publishConfig": {
    "access": "restricted",
    "registry": "https://registry.npmjs.org/"
  }
}

✅ Correct

{
  "name": "@scope/my-package",
  "publishConfig": {
    "access": "public"
  }
}

{
  "name": "my-package",
  "publishConfig": {
    "registry": "https://registry.npmjs.org/"
  }
}

When Not To Use It

If a package intentionally keeps publishConfig.access as documentation for a future move to a scoped package, this rule might not be for you.

Further Reading

• npm: publishConfig
• npm: npm publish

Equivalents in Other Linters

• ESLint: package-json/no-redundant-publishConfig