← Home

@mongodb-js/get-os-info

npm Repository Homepage

Get os info for telemetry

15
Versions
Apache-2.0
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

mongodb-js-useralexander_schrollmbroadsthswolffsatyasinhajeff-allen-mongojonathan.balsanomongodb-buildjack.weirkristina.stefanojarjeeshaketbabydevtoolsbotgribnoysupmutukrishmongo-jdariakpaddaleaxnbbeekendbx-nodenirinchevpearsb1mcasimir_mdb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): mcasimir_mdb appears to be a renamed account of mcasimir within MongoDB org; not a third-party takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of mcasimir paired with addition of mcasimir_mdb indicates account rename, not hostile takeover. ai
bogus-package bogus-package AI (bogus-package): MongoDB-js org publishes many templated packages; mass-production signal is a stable false positive here. ai

Versions (showing 15 of 15)

Version Deps Published
0.6.11 0 / 17
0.6.10 0 / 17
0.6.9 0 / 17
0.6.8 0 / 17
0.6.7 0 / 17
0.6.6 0 / 17
0.6.5 0 / 17
0.6.4 0 / 17
0.6.3 0 / 17
0.6.0 0 / 17
0.5.4 0 / 17
0.5.3 0 / 17
0.5.2 0 / 17
0.5.1 0 / 17
0.5.0 0 / 17

v0.6.11

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.

v0.6.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.8

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.

v0.6.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

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.

v0.5.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

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.