@mappies/miniwat-mcp-web
MCP for web related tools
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mdream | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect/config-based imports for this package. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): Known implicit/runtime dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dommatrix | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on config-based imports. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on config-based imports. | ai | |
| phantom-deps | phantom-dep:@tavily/core | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on config-based imports. | ai | |
| phantom-deps | phantom-dep:markitdown-ts | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on config-based imports. | ai | |
| phantom-deps | phantom-dep:unzipper | AI (phantom-deps): unzipper is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 7 / 5 | |
| 0.13.0 | 7 / 5 | |
| 0.12.0 | 7 / 5 | |
| 0.11.0 | 7 / 5 | |
| 0.10.0 | 7 / 5 | |
| 0.9.0 | 7 / 5 | |
| 0.8.0 | 7 / 5 | |
| 0.7.0 | 7 / 5 | |
| 0.6.0 | 6 / 5 | |
| 0.5.0 | 6 / 5 | |
| 0.4.0 | 6 / 5 | |
| 0.3.0 | 6 / 5 | |
| 0.2.0 | 6 / 5 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 |
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.