@wisemen/wise-invoicing
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Wisemen org package; 0.0.0 reflects early/pre-release versioning, not throwaway malware pattern. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): ESLint and its plugins are peer/config deps, not directly imported in source — expected pattern for this package type. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unicorn | AI (phantom-deps): ESLint plugin used via config, not direct import — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@wisemen/eslint-config-nestjs | AI (phantom-deps): Same-org ESLint config dep; used via config reference, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import-typescript | AI (phantom-deps): ESLint plugin used via config, not direct import — stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 4 / 6 | |
| 0.0.4 | 8 / 2 | |
| 0.0.2 | 8 / 2 | |
| 0.0.1 | 8 / 2 | |
| 0.0.0 | 8 / 2 |
v0.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yuhanghu) than the most recent previously approved version (kobe-kwanten-wisemen) on 2026-05-26, but yuhanghu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kobe-kwanten-wisemen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.