← Home

@wildboar/rose

npm Repository Homepage

Remote Operation Service Element PDUs in TypeScript

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jonathanwilbur

Keywords

roseremoteoperationserviceelementrpc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@wildboar/asn1 AI (dependencies): Same-org JSR-aliased dependency; consistent with the package's own ecosystem and author. ai
provenance no-provenance AI (provenance): Established package predating common provenance adoption; no other risk signals present. ai

Versions (showing 3 of 3)

Version Deps Published
2.0.2 3 / 0
2.0.1 3 / 0
2.0.0 3 / 0

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.