@primate/marko
Marko for Primate
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@marko/translator-default | AI (phantom-deps): Used as a compiler translator config reference, not a direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@rcompat/fs | AI (phantom-deps): @rcompat/fs is a declared runtime dependency in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 4 / 3 | |
| 0.9.0 | 4 / 1 | |
| 0.8.0 | 4 / 2 | |
| 0.7.0 | 4 / 1 | |
| 0.6.0 | 4 / 1 | |
| 0.3.0 | 4 / 1 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.