nanoscheduler
Schedule work to be completed when the browser is idle.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change to goto-bus-stop occurred in 2018 as part of a legitimate choojs community transition. Publisher has strong track record (1219 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Large maintainer list reflects the choojs/hypermodules open-source collective. Transition occurred in 2018 and is well-established. | ai | |
| phantom-deps | phantom-dep:nanoassert | AI (phantom-deps): nanoassert is used via the browser field alias for 'assert', not a direct require. This is a standard browser bundler pattern; not a true phantom dependency. | ai |
v1.0.3
2 findingsThis version was published by a different npm account than previous versions on 2018-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.