@walkeros/mcp-source-browser
MCP server for walkerOS data-elb HTML tagging — generate, parse, and validate tracking attributes with real DOM parsing
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD with SLSA attestation; consistent with monorepo automation. | ai | |
| provenance | no-provenance | AI (provenance): Established walkerOS monorepo package; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@walkeros/core | AI (dependencies): Sibling package in the same walkerOS monorepo; unvetted status reflects review lag, not independent risk. | ai | |
| dependencies | unvetted-dep:@walkeros/web-source-browser | AI (dependencies): Sibling package in the same walkerOS monorepo; unvetted status reflects review lag, not independent risk. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 4 / 5 | |
| 4.1.1 | 4 / 5 | |
| 4.1.0 | 4 / 5 | |
| 4.0.2 | 4 / 5 | |
| 4.0.1 | 4 / 5 | |
| 4.0.0 | 4 / 5 | |
| 3.4.2 | 4 / 5 | |
| 3.4.1 | 4 / 5 | |
| 3.4.0 | 4 / 5 | |
| 3.3.1 | 4 / 5 | |
| 3.3.0 | 4 / 5 | |
| 3.2.0 | 4 / 5 | |
| 3.1.1 | 4 / 5 | |
| 3.1.0 | 4 / 5 | |
| 3.0.2 | 4 / 5 | |
| 3.0.1 | 3 / 6 | |
| 3.0.0 | 3 / 6 | |
| 0.1.0 | 3 / 6 |
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.