@lindorm/create-pylon
Interactive CLI scaffolder for new [Pylon](https://www.npmjs.com/package/@lindorm/pylon) applications.
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 | no-provenance | AI (provenance): Consistent across all @lindorm/* packages from this publisher; not a per-version concern. | ai | |
| phantom-deps | phantom-dep:@lindorm/case | AI (phantom-deps): Same-org package, likely used as types/utilities; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@lindorm/types | AI (phantom-deps): Same-org types package; declared for type resolution, stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 9 / 1 | |
| 0.5.0 | 9 / 1 | |
| 0.4.1 | 9 / 1 | |
| 0.4.0 | 9 / 1 | |
| 0.2.0 | 9 / 1 | |
| 0.1.0 | 9 / 1 |
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.