@bonniernews/mcp-server
Wrapper for creating MCP servers
4
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
markusnmxtrmatsrorbeckerdan.karlssonjonaswaldenmarie-winthermarcusgronbladaxeljohanssonbonniernewskarlbergcchavahjoelekmanadam.hakanssonhillesoguslidenandreas.samuelssonjzachrissonnorlavarneynzalicebobergjoharknifoherbolavitryssentakolandermorremikael.mattssonschristianssonbnmattiasobndaghalleranderssonjonaekamundsentbdrgeobnoscartholanderpeterpetterssonliroliroollenolletorkelbergetnblomjackesaemilbjorklundlilianjkristofferjanssonkitgusodynvolk
Keywords
MCPMCP serverModel Context ProtocolAPI serverHTTP APIExpressNode.jsdynamic toolsstatic toolsmiddlewareTypeScriptAtom APIJSON Schemaserver wrappertool registryAPI toolsdynamic APIrequest validationserver frameworkBonnier News
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Org-scoped BonnierNews package; lack of provenance is common and no other risk signals present. | ai | |
| phantom-deps | phantom-dep:supertest | AI (phantom-deps): supertest is a test utility; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/supertest | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 7 / 16 | |
| 0.2.3 | 7 / 16 | |
| 0.0.6 | 5 / 15 | |
| 0.0.4 | 5 / 15 |
v0.2.3
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.0.6
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.
v0.0.4
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.