osc-js
OSC library for Node.js and the browser, with customizable Plugin API for WebSocket, UDP or bridge networking
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:marmorkuchen.net | AI (email-domain): Long-established package (9+ years, 25 versions) with consistent history. Lapsed email domain is a theoretical risk but no evidence of exploitation or account compromise. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package predating Sigstore; no provenance is expected and consistent across all versions. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a legitimate runtime dependency; isomorphic-ws wraps ws, making the explicit ws dep a valid direct declaration for this WebSocket/UDP library. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 1 / 22 | |
| 2.4.0 | 1 / 22 | |
| 2.3.2 | 1 / 18 | |
| 2.3.1 | 2 / 17 | |
| 2.3.0 | 2 / 17 | |
| 2.2.0 | 2 / 16 | |
| 2.1.2 | 2 / 16 | |
| 2.1.1 | 2 / 16 | |
| 2.1.0 | 2 / 16 | |
| 2.0.4 | 2 / 16 | |
| 2.0.3 | 2 / 16 | |
| 2.0.2 | 2 / 16 | |
| 2.0.1 | 2 / 16 | |
| 2.0.0 | 2 / 16 | |
| 1.2.2 | 1 / 16 | |
| 1.2.0 | 1 / 18 | |
| 1.1.1 | 1 / 18 | |
| 1.1.0 | 1 / 18 | |
| 1.0.6 | 1 / 18 | |
| 1.0.5 | 1 / 17 | |
| 1.0.4 | 1 / 17 | |
| 1.0.3 | 1 / 16 | |
| 1.0.2 | 1 / 16 | |
| 1.0.1 | 1 / 16 | |
| 1.0.0 | 1 / 16 |
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsMaintainer email '[email protected]' uses domain 'marmorkuchen.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.