@arthur2079/docs
First, run the development server:
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:@repo/ui | AI (phantom-deps): Internal monorepo dep; phantom-dep false positive stable for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped org docs package; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:next | AI (phantom-deps): Next.js docs app; framework consumed via config, not direct imports. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React used implicitly in Next.js docs app context. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom used implicitly in Next.js docs app context. | ai | |
| phantom-deps | phantom-dep:@arthur2079/ui | AI (phantom-deps): Same-org UI package; likely consumed via config or MDX, not direct import. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.27.0 | 4 / 7 | |
| 3.26.1 | 4 / 7 | |
| 3.26.0 | 4 / 7 | |
| 3.25.0 | 4 / 7 | |
| 3.24.0 | 4 / 7 | |
| 3.23.3 | 4 / 7 | |
| 3.23.2 | 4 / 7 | |
| 3.23.1 | 4 / 7 | |
| 3.23.0 | 4 / 7 | |
| 3.22.1 | 4 / 7 | |
| 3.22.0 | 4 / 7 | |
| 3.21.0 | 4 / 7 | |
| 2.20.0 | 4 / 7 |
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.