@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known-maintainer manual publish, not an attested lineage regression. | ai | |
| dependencies | unvetted-dep:@wisemen/nestjs-custom-fields | AI (dependencies): Same-org first-party dependency, consistent with package's own scope. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is a style issue, not a malice indicator for this publisher. | ai | |
| 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-import-typescript | 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-unicorn | AI (phantom-deps): ESLint plugin used via config, not direct import — stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.0.14 | 3 / 8 | |
| 0.0.13 | 4 / 8 | |
| 0.0.12 | 4 / 8 | |
| 0.0.11 | 3 / 8 | |
| 0.0.10 | 3 / 8 | |
| 0.0.9 | 3 / 7 | |
| 0.0.8 | 4 / 6 | |
| 0.0.7 | 4 / 6 | |
| 0.0.6 | 4 / 6 | |
| 0.0.5 | 8 / 2 | |
| 0.0.4 | 8 / 2 | |
| 0.0.3 | 8 / 2 | |
| 0.0.2 | 8 / 2 | |
| 0.0.1 | 8 / 2 | |
| 0.0.0 | 8 / 2 |
v0.0.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yuhanghu.
v0.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yuhanghu.
v0.0.12
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: yuhanghu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
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: yuhanghu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yuhanghu.
Package 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-04-29, 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.3
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-04-23, 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.