docz-utils
Some methods used and utilities used on 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 | publisher-changed | AI (provenance): Publisher change from pedronauck to rakannimer occurred in Nov 2019 (5+ years ago) and reflects a legitimate maintainer transition within the docz project team. rakannimer is a known docz contributor. | ai | |
| phantom-deps | phantom-dep:unescape-js | AI (phantom-deps): unescape-js is declared as a runtime dependency in package.json; phantom-dep detection is a false positive for this utility library. | ai | |
| phantom-deps | phantom-dep:unist-util-is | AI (phantom-deps): unist-util-is is declared as a runtime dependency in package.json; phantom-dep detection is a false positive for this utility library. | ai | |
| bogus-package | bogus-package | AI (bogus-package): docz-utils is a monorepo sub-package with 83 versions and 7.4k weekly downloads; sparse README and no keywords are typical for internal utility packages. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 22 / 0 | |
| 2.3.0 | 22 / 3 | |
| 2.1.0 | 22 / 3 | |
| 2.0.0 | 22 / 3 | |
| 1.2.0 | 23 / 1 | |
| 1.1.0 | 23 / 1 | |
| 1.0.4 | 23 / 1 | |
| 1.0.2 | 23 / 1 | |
| 1.0.1 | 23 / 1 | |
| 1.0.0 | 23 / 0 | |
| 0.13.6 | 23 / 0 | |
| 0.13.5 | 23 / 0 | |
| 0.13.3 | 22 / 0 | |
| 0.13.0 | 22 / 0 | |
| 0.12.16 | 22 / 2 | |
| 0.12.15 | 22 / 2 | |
| 0.12.14 | 22 / 2 | |
| 0.12.13 | 22 / 2 | |
| 0.12.12 | 22 / 2 | |
| 0.12.10 | 22 / 2 | |
| 0.12.9 | 21 / 2 | |
| 0.12.8 | 21 / 2 | |
| 0.12.6 | 21 / 2 | |
| 0.12.2 | 21 / 2 |
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.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2019-11-27. 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.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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.