marko
UI Components + streaming, async, high performance, HTML templating for Node.js and the browser.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:csstype | AI (phantom-deps): csstype is used as a type-only import in tags-html.d.ts; scanner misses .d.ts imports — stable FP for this package. | ai | |
| vendored-integrity | unresolved-vendored-tree:dist/node_modules/@internal/require | AI (vendored-integrity): Internal build shim, no manifest expected; consistent with Marko's compiler tooling. | ai | |
| vendored-integrity | unresolved-vendored-tree:dist/node_modules/@internal/set-immediate | AI (vendored-integrity): Internal build shim, no manifest expected; consistent with Marko's compiler tooling. | ai | |
| vendored-integrity | unresolved-vendored-tree:src/node_modules/@internal/require | AI (vendored-integrity): Internal build shim, mirrors dist counterpart. | ai | |
| vendored-integrity | unresolved-vendored-tree:src/node_modules/@internal/set-immediate | AI (vendored-integrity): Internal build shim, mirrors dist counterpart. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All added deps are well-known, long-published packages tied to the runtime-tags refactor. | ai | |
| provenance | publisher-changed | AI (provenance): marko migrated to GitHub Actions CI/CD publishing with SLSA attestation; publisher-changed from human to GHA is expected and desirable for this package. | ai | |
| source-diff | obfuscated-file:dist/translator/interop/index.d.ts | AI (source-diff): The file is a TypeScript .d.ts declaration with a long union type of Babel AST node names — not obfuscated code. Long lines are inherent to exhaustive AST type unions in compiler tooling. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): marko v6 is a new runtime series under the same package name; apparent dormancy reflects the v5→v6 transition, not account takeover. SLSA attestation confirms legitimate provenance. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in parse-module-code.js is part of Marko's template compiler pipeline for evaluating module expressions — expected behavior for a template engine, not a supply-chain risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in markoc.js loads marko/package.json to read the version string — a benign, stable pattern in this package's CLI tooling. | ai |
Versions (showing 51 of 153)
| Version | Deps | Published |
|---|---|---|
| 6.3.17 | 4 / 2 | |
| 6.3.16 | 4 / 0 | |
| 6.3.15 | 4 / 0 | |
| 6.3.14 | 4 / 0 | |
| 6.3.13 | 4 / 0 | |
| 6.3.12 | 4 / 0 | |
| 6.3.11 | 4 / 0 | |
| 6.3.10 | 4 / 0 | |
| 6.3.9 | 4 / 0 | |
| 6.3.8 | 4 / 0 | |
| 6.3.7 | 4 / 0 | |
| 6.3.6 | 4 / 0 | |
| 6.3.5 | 4 / 0 | |
| 6.3.4 | 4 / 0 | |
| 6.3.3 | 4 / 0 | |
| 6.3.2 | 4 / 0 | |
| 6.3.1 | 4 / 0 | |
| 6.3.0 | 4 / 0 | |
| 6.2.5 | 4 / 0 | |
| 6.2.4 | 4 / 0 | |
| 6.2.3 | 4 / 0 | |
| 6.2.2 | 4 / 0 | |
| 6.2.1 | 4 / 0 | |
| 6.2.0 | 4 / 0 | |
| 6.1.24 | 4 / 0 | |
| 6.1.23 | 4 / 0 | |
| 6.1.22 | 4 / 0 | |
| 6.1.21 | 4 / 0 | |
| 6.1.20 | 4 / 0 | |
| 6.1.18 | 4 / 0 | |
| 6.1.17 | 4 / 0 | |
| 6.1.16 | 4 / 0 | |
| 6.1.15 | 4 / 0 | |
| 6.1.14 | 4 / 0 | |
| 6.1.13 | 4 / 0 | |
| 6.1.12 | 4 / 0 | |
| 6.1.11 | 4 / 0 | |
| 6.1.10 | 4 / 0 | |
| 6.1.9 | 4 / 0 | |
| 6.1.8 | 4 / 0 | |
| 6.1.7 | 4 / 0 | |
| 6.1.6 | 4 / 0 | |
| 6.1.5 | 4 / 0 | |
| 6.1.4 | 4 / 0 | |
| 6.1.3 | 4 / 0 | |
| 6.1.2 | 4 / 0 | |
| 6.1.1 | 4 / 0 | |
| 6.1.0 | 4 / 0 | |
| 6.0.173 | 4 / 0 | |
| 6.0.172 | 4 / 0 | |
| 6.0.171 | 4 / 0 |
v6.3.17
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
The directory `.` byte-matched 159 of 179 file(s) against [email protected] — a version that passed review and that we hold in storage — which identifies it as a vendored copy of that package. But 19 file(s) inside it differ from that package's bytes at the same path: dist/common/accessor.d.ts, dist/common/accessor.debug.d.ts, dist/common/types.d.ts, dist/debug/dom.js, dist/debug/dom.mjs, dist/debug/html.js, dist/debug/html.mjs, dist/dom.js, dist/dom.mjs, dist/html.d.ts, dist/html.js, dist/html.mjs, dist/html/attrs.d.ts, dist/translator/index.js, dist/translator/util/body-to-text-literal.d.ts, dist/translator/util/to-first-expression-or-block.d.ts, dist/translator/util/walks.d.ts, dist/translator/util/writer.d.ts, package.json. A vendored library that is a faithful copy except for a handful of altered files is a well-worn supply-chain shape — the surrounding real code lends the tree legitimacy while the altered files carry the payload. These files are NOT exempt from any authorship heuristic; diff them against [email protected] before greenflagging.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.