Protect npm publishing with account 2FA and a scoped release path
Secure the maintainer account, review package publishing access and use supported trusted publishing where appropriate.
Recognize online traps, review account access and improve everyday security with practical defensive guidance.
Search this section ↗76 topics in this section.
Secure the maintainer account, review package publishing access and use supported trusted publishing where appropriate.
Compare the exact registry name with the project’s official instructions, then inspect metadata and lifecycle scripts before installing.
Check origin, build and distribution, update policy and the permissions a dependency gains in your environment.
Separate untrusted checks from privileged releases, scope workflow permissions and review third-party actions as executable dependencies.
Separate everyday access from administration, grant permissions for a defined task and review access when the task ends.
Protect the recovery owner, use roles for day-to-day access and give workloads their own limited credentials.
Record sign-ins, permission changes and privileged actions, protect the logs and make sure a harmless test event appears.
Preserve evidence, protect the hosting and domain accounts and recover from a verified clean version without overwriting the investigation.
Check device encryption, preserve its recovery key and distinguish powered-off data protection from account and malware security.
Inspect camera, microphone, location and contacts access, use narrower options where available and test the affected feature.
Check the screen lock, device locator, backup and recovery methods while the phone is still in your hands.
Understand tags versus immutable commit references, verify the resolved action and keep pinned dependencies maintainable.
Track browsers, operating systems, routers and other connected devices, with owners and support status instead of relying on one notification.
Inspect the exact new package and lockfile resolution before installation or deployment, rather than trusting a plausible generated import.
Read scope, affected systems and mitigations, then map the advisory to your real assets instead of copying every recommendation indiscriminately.
Use the identifier to find the vendor advisory, check affected versions and conditions and distinguish severity from proven exposure.
Read Apple’s architecture and 2026 expansion, distinguish PCC processing from separate third-party integrations and review the data path of the feature used.
Understand the opt-in reference capture system, distinguish an authenticated capture from a truthful interpretation and keep privacy clues in view.