wikiparser-node
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/bin/config.js | AI (source-diff): Documented CLI bin fetching MediaWiki config; matches package's stated function. | ai | |
| source-diff | net-exec-file:dist/lib/document.js | AI (source-diff): fetch() is a schema-resolution callback for a JSON language service, not dropper/exfil behavior. | ai | |
| dependencies | unvetted-dep:codejar-async | AI (dependencies): Legit code-editor lib used by this package's browser editor extension. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived package with 220 versions; no provenance has been a stable characteristic. | ai | |
| license | copyleft-license:GPL-3.0-or-later | AI (license): GPL-3.0 is the declared license for this package; not a security concern. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 1.46.1 | 7 / 29 | |
| 1.46.0 | 6 / 30 | |
| 1.45.0 | 6 / 30 | |
| 1.44.0 | 6 / 33 | |
| 1.43.0 | 7 / 29 | |
| 1.42.0 | 6 / 23 | |
| 1.41.0 | 6 / 23 | |
| 1.40.0 | 6 / 24 | |
| 1.39.1 | 6 / 32 | |
| 1.39.0 | 6 / 32 | |
| 1.38.1 | 6 / 31 | |
| 1.37.1 | 5 / 32 | |
| 1.37.0 | 5 / 32 | |
| 1.36.0 | 5 / 32 | |
| 1.35.2 | 5 / 32 | |
| 1.35.1 | 5 / 32 | |
| 1.35.0 | 5 / 32 | |
| 1.34.0 | 5 / 32 | |
| 1.33.0 | 5 / 32 | |
| 1.32.0 | 5 / 32 | |
| 1.31.0 | 5 / 31 | |
| 1.30.0 | 5 / 28 | |
| 1.29.2 | 5 / 28 | |
| 1.29.1 | 5 / 28 | |
| 1.29.0 | 5 / 28 | |
| 1.28.1 | 4 / 28 | |
| 1.28.0 | 4 / 28 | |
| 1.27.1 | 4 / 28 | |
| 1.27.0 | 4 / 28 | |
| 1.26.0 | 4 / 28 | |
| 1.25.1 | 4 / 28 | |
| 1.25.0 | 4 / 28 | |
| 1.24.1 | 4 / 28 | |
| 1.24.0 | 4 / 28 | |
| 1.23.0 | 4 / 28 | |
| 1.22.1 | 4 / 28 | |
| 1.22.0 | 4 / 28 | |
| 1.21.3 | 2 / 26 | |
| 1.21.2 | 2 / 26 | |
| 1.21.1 | 2 / 26 | |
| 1.21.0 | 2 / 28 | |
| 1.20.3 | 2 / 28 | |
| 1.20.2 | 2 / 28 | |
| 1.20.1 | 2 / 30 | |
| 1.20.0 | 2 / 30 | |
| 1.19.0 | 2 / 30 | |
| 1.18.4 | 2 / 30 | |
| 1.18.3 | 2 / 30 | |
| 1.18.2 | 2 / 30 | |
| 1.18.1 | 2 / 30 | |
| 1.18.0 | 2 / 29 | |
| 1.17.1 | 5 / 25 | |
| 1.17.0 | 7 / 26 | |
| 1.16.6 | 7 / 26 | |
| 1.16.5 | 7 / 26 | |
| 1.16.4 | 7 / 26 | |
| 1.16.3 | 7 / 26 | |
| 1.16.2 | 7 / 26 | |
| 1.16.1 | 7 / 25 | |
| 1.16.0 | 7 / 25 | |
| 1.15.1 | 6 / 24 | |
| 1.15.0 | 5 / 23 | |
| 1.14.1 | 5 / 23 | |
| 1.14.0 | 2 / 24 | |
| 1.13.9 | 2 / 24 | |
| 1.13.8 | 2 / 24 | |
| 1.13.7 | 1 / 25 | |
| 1.13.6 | 1 / 25 | |
| 1.13.5 | 1 / 25 | |
| 1.13.4 | 1 / 6 | |
| 1.13.3 | 1 / 6 | |
| 1.13.2 | 1 / 6 | |
| 1.13.1 | 1 / 6 | |
| 1.13.0 | 1 / 6 | |
| 1.12.7 | 1 / 6 | |
| 1.12.6 | 1 / 6 | |
| 1.12.5 | 1 / 6 | |
| 1.12.4 | 1 / 6 | |
| 1.12.3 | 1 / 6 | |
| 1.12.2 | 1 / 6 | |
| 1.11.1 | 1 / 5 | |
| 1.11.0 | 1 / 18 | |
| 1.10.0 | 1 / 18 | |
| 1.9.3 | 1 / 18 | |
| 1.9.2 | 1 / 18 | |
| 1.9.1 | 1 / 18 | |
| 1.9.0 | 1 / 18 | |
| 1.8.0 | 1 / 20 | |
| 1.7.1 | 1 / 20 | |
| 1.7.0 | 1 / 20 |
v1.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.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.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.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.