@donotdev/templates
Page templates for common use cases in DoNotDev
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@donotdev/components | AI (phantom-deps): Same-org monorepo package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@donotdev/crud | AI (phantom-deps): Same-org monorepo package; declared deps used transitively, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Referenced in config files; monorepo pattern, not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@donotdev/adv-comps | AI (phantom-deps): Same-org monorepo package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Referenced in config files; monorepo pattern, not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Referenced in config/build files; stable false positive for this template package. | ai | |
| phantom-deps | phantom-dep:marked-footnote | AI (phantom-deps): Referenced in config/build files; stable false positive for this template package. | ai | |
| phantom-deps | phantom-dep:html-react-parser | AI (phantom-deps): Referenced in config/build files; stable false positive for this template package. | ai | |
| phantom-deps | phantom-dep:@donotdev/ui | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in analyzed files. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.1.42 | 6 / 0 | |
| 0.1.1 | 7 / 0 | |
| 0.1.0 | 7 / 0 | |
| 0.0.22 | 7 / 0 | |
| 0.0.21 | 7 / 0 | |
| 0.0.20 | 7 / 0 | |
| 0.0.19 | 7 / 0 | |
| 0.0.18 | 8 / 0 | |
| 0.0.17 | 8 / 0 | |
| 0.0.16 | 8 / 0 | |
| 0.0.15 | 8 / 0 | |
| 0.0.14 | 8 / 0 | |
| 0.0.6 | 9 / 0 | |
| 0.0.5 | 9 / 0 | |
| 0.0.3 | 8 / 0 |
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.