remark-docz
Remark plugin used by docz
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Long-established package with 74 versions; missing gitHead reflects a CI/publish environment change, not a security concern. No behavioral risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence is expected for this era of publishing and not a security indicator for this well-established package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from rakannimer to renatobenks reflects the documented docz project maintainer transition; renatobenks is the active docz maintainer with a clean track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): renatobenks is the active docz project maintainer; addition is consistent with legitimate project ownership transfer. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are cosmetic issues, not spam indicators for this established package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 4 / 0 | |
| 2.1.0 | 4 / 3 | |
| 2.0.0 | 4 / 3 | |
| 1.2.0 | 4 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.4 | 2 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 1 | |
| 0.13.3 | 2 / 0 | |
| 0.13.0 | 2 / 0 | |
| 0.12.15 | 2 / 0 | |
| 0.12.14 | 2 / 0 | |
| 0.12.2 | 2 / 0 | |
| 0.11.0 | 2 / 0 | |
| 0.9.4 | 2 / 0 | |
| 0.9.0 | 2 / 0 | |
| 0.7.0 | 2 / 0 |
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2022-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
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: rakannimer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.