@rsdoctor/core
This is the core package of Rsdoctor, providing core tools and analysis capabilities for Rsdoctor plugins.
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 |
|---|---|---|---|---|
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Comment in bundled axios/debug code referencing /etc/passwd in a test example; not actual access. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package; low-value README signals are false positives. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI is documented by SLSA attestation; expected for this org's release automation. | ai | |
| phantom-deps | phantom-dep:webpack-bundle-analyzer | AI (phantom-deps): webpack-bundle-analyzer is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Fires inside vendored debug library filtering only DEBUG_* keys; benign config pattern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped monorepo package @rsdoctor/core; no relation to the 'cors' package. Stable false positive. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.5.12 | 12 / 14 | |
| 1.5.11 | 12 / 14 | |
| 1.5.10 | 12 / 14 | |
| 1.5.9 | 12 / 14 | |
| 1.5.8 | 12 / 14 | |
| 1.5.7 | 12 / 15 | |
| 1.5.6 | 12 / 15 | |
| 1.5.5 | 12 / 15 | |
| 1.5.4 | 12 / 15 | |
| 1.5.3 | 12 / 15 | |
| 1.5.2 | 12 / 15 | |
| 1.5.1 | 12 / 15 | |
| 1.5.0 | 12 / 15 | |
| 1.4.0 | 12 / 15 | |
| 1.3.16 | 12 / 15 | |
| 1.3.15 | 12 / 15 | |
| 1.3.14 | 12 / 15 | |
| 1.3.13 | 12 / 15 | |
| 1.3.12 | 12 / 15 | |
| 1.3.11 | 12 / 15 | |
| 1.3.10 | 12 / 15 | |
| 1.3.9 | 12 / 15 | |
| 1.3.8 | 12 / 15 | |
| 1.3.7 | 12 / 15 | |
| 1.3.6 | 12 / 15 | |
| 1.3.5 | 12 / 15 | |
| 1.3.4 | 11 / 16 | |
| 1.3.3 | 12 / 16 | |
| 1.3.2 | 12 / 16 | |
| 1.2.3 | 14 / 16 | |
| 1.2.2 | 15 / 16 | |
| 1.2.1 | 15 / 16 | |
| 1.2.0 | 15 / 16 | |
| 1.1.11 | 15 / 15 | |
| 1.1.10 | 15 / 15 | |
| 1.1.9 | 15 / 15 | |
| 1.1.8 | 15 / 15 | |
| 1.1.7 | 15 / 15 | |
| 1.1.6 | 15 / 15 | |
| 1.1.5 | 15 / 15 | |
| 1.1.4 | 15 / 15 | |
| 1.1.3 | 15 / 15 | |
| 1.1.2 | 15 / 15 | |
| 1.1.1 | 15 / 15 | |
| 1.1.0 | 15 / 15 |
v1.5.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.11
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.10
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.9
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.8
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.7
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.5
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.4
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.3
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.13
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.12
2 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.11
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.10
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.9
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.8
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.7
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.5
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.4
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.3
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.2
3 findingsPackage name '@rsdoctor/core' is 1 edit(s) away from popular package 'cors'.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 1358 | // stream from an existing fd which is writable only. But for now 1359 | // we'll just add this hack and set the `readable` member to false. > 1360 | // Test: ./node test/fixtures/echo.js < /etc/passwd 1361 | stream.readable = false; 1362 | stream.read = null;
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-08-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.11
2 findingsThis version was published by a different npm account than previous versions on 2025-08-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.