@nano-island/create-plugin
Nano Island 插件系统 CLI 脚手架
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:shelljs | AI (phantom-deps): shelljs is in both dependencies and devDependencies; phantom-dep fires as a false positive for this package. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): CLI tool; glob is a runtime dep used for file globbing. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): CLI tool; chalk is a runtime dep used for terminal colors. | ai | |
| phantom-deps | phantom-dep:giget | AI (phantom-deps): CLI tool; giget is a runtime dep used for template scaffolding. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI tool; ora is a runtime dep used for spinners, not a phantom dep. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI tool; commander is a runtime dep used for CLI argument parsing. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): CLI tool; @inquirer/prompts is a runtime dep used for interactive prompts. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): CLI tool; fs-extra is a runtime dep used for file operations. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.16 | 7 / 2 | |
| 1.0.13 | 9 / 5 | |
| 1.0.12 | 9 / 5 | |
| 1.0.11 | 9 / 5 | |
| 1.0.10 | 9 / 5 | |
| 1.0.9 | 9 / 5 | |
| 1.0.8 | 9 / 5 | |
| 1.0.7 | 9 / 5 | |
| 1.0.6 | 8 / 5 | |
| 1.0.5 | 8 / 5 | |
| 1.0.4 | 7 / 4 | |
| 1.0.3 | 7 / 4 | |
| 1.0.2 | 7 / 4 | |
| 1.0.1 | 7 / 4 | |
| 1.0.0 | 7 / 4 |
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
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.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.