@dxos/node-std
Simple wrapper for browser replacements of node stdlib modules within the DXOS codebase.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:util | AI (phantom-deps): util is a declared runtime dep re-exported as a browser polyfill; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:assert | AI (phantom-deps): assert is a declared runtime dep re-exported as a browser polyfill; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:events | AI (phantom-deps): events is a declared runtime dep re-exported as a browser polyfill; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): path-browserify is a declared runtime dep re-exported as a browser polyfill; not a phantom dep. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 5 / 1 | |
| 0.9.0 | 5 / 1 | |
| 0.8.3 | 5 / 1 | |
| 0.8.2 | 5 / 1 | |
| 0.8.1 | 5 / 1 | |
| 0.8.0 | 5 / 1 | |
| 0.7.4 | 5 / 1 | |
| 0.7.3 | 5 / 1 | |
| 0.7.2 | 5 / 1 | |
| 0.7.1 | 5 / 1 | |
| 0.7.0 | 5 / 1 | |
| 0.6.13 | 5 / 1 | |
| 0.6.12 | 5 / 1 | |
| 0.6.11 | 5 / 1 | |
| 0.6.10 | 5 / 1 | |
| 0.6.9 | 5 / 1 | |
| 0.6.8 | 5 / 1 | |
| 0.6.7 | 5 / 1 | |
| 0.6.6 | 5 / 1 | |
| 0.6.5 | 5 / 1 | |
| 0.6.4 | 5 / 1 | |
| 0.6.3 | 5 / 1 | |
| 0.6.2 | 5 / 1 | |
| 0.6.1 | 5 / 1 | |
| 0.6.0 | 5 / 1 | |
| 0.5.8 | 5 / 1 | |
| 0.5.7 | 5 / 1 | |
| 0.5.6 | 5 / 1 | |
| 0.5.5 | 5 / 1 | |
| 0.5.4 | 5 / 1 | |
| 0.5.3 | 5 / 1 | |
| 0.5.2 | 5 / 1 |
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.