← Home

@mongodb-js/get-os-info

npm Repository Homepage

Get os info for telemetry

22
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

satyasinhakristina.stefanojarjeedevtoolsbotmongo-jnbbeekendbx-nodedevtools-npm-user

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 22 of 22)

Version Deps Published
0.7.1 0 / 17
0.7.0 0 / 17
0.6.12 0 / 17
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
0.4.1 0 / 17
0.4.0 0 / 17
0.3.25 0 / 17
0.3.24 0 / 17

v0.7.1

1 finding
LOW No provenance attestation provenance

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

v0.7.0

2 findings
HIGH Publisher changed: gribnoysup → devtools-npm-user (on 2026-07-16) provenance

This version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.6.12

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: devtoolsbot → gribnoysup (on 2026-06-30, known maintainer) provenance

This version was published by a different npm account (gribnoysup) than the most recent previously approved version (devtoolsbot) on 2026-06-30, but gribnoysup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.25

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.3.24

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.