@wisemen/monetary
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher; SLSA provenance attestation confirms legitimate automated publish pipeline. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with GitHub Actions publish flow that uses SLSA provenance instead; not a risk indicator here. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI/CD with Sigstore attestation; strong supply chain integrity signal. | ai | |
| phantom-deps | phantom-dep:@wisemen/nestjs-typeorm | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly. Stable false positive for this package. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 1 / 7 | |
| 0.5.2 | 1 / 7 | |
| 0.5.1 | 1 / 7 | |
| 0.5.0 | 1 / 7 | |
| 0.4.7 | 1 / 7 | |
| 0.4.6 | 1 / 7 | |
| 0.4.5 | 1 / 7 | |
| 0.4.4 | 1 / 5 | |
| 0.4.3 | 1 / 5 | |
| 0.4.2 | 1 / 5 | |
| 0.4.1 | 1 / 5 | |
| 0.4.0 | 1 / 5 | |
| 0.3.0 | 0 / 7 | |
| 0.2.36 | 0 / 7 | |
| 0.2.35 | 0 / 7 | |
| 0.2.34 | 0 / 7 | |
| 0.2.33 | 0 / 7 | |
| 0.2.32 | 0 / 7 | |
| 0.2.31 | 0 / 7 | |
| 0.2.30 | 0 / 7 | |
| 0.2.29 | 6 / 7 | |
| 0.2.28 | 6 / 7 | |
| 0.2.27 | 6 / 7 | |
| 0.2.26 | 6 / 7 | |
| 0.2.25 | 6 / 7 | |
| 0.2.24 | 6 / 8 | |
| 0.2.23 | 6 / 8 | |
| 0.2.22 | 6 / 8 | |
| 0.2.21 | 6 / 8 | |
| 0.2.20 | 5 / 8 | |
| 0.2.19 | 5 / 8 | |
| 0.2.18 | 5 / 8 | |
| 0.2.17 | 5 / 8 | |
| 0.2.16 | 5 / 8 | |
| 0.2.15 | 5 / 8 | |
| 0.2.14 | 5 / 8 | |
| 0.2.13 | 5 / 8 | |
| 0.2.12 | 5 / 8 | |
| 0.2.11 | 5 / 8 | |
| 0.2.10 | 5 / 4 | |
| 0.2.9 | 5 / 4 | |
| 0.2.8 | 5 / 4 | |
| 0.2.7 | 5 / 4 | |
| 0.2.6 | 5 / 4 | |
| 0.2.5 | 5 / 4 | |
| 0.2.4 | 5 / 4 | |
| 0.2.3 | 5 / 4 | |
| 0.2.2 | 5 / 4 | |
| 0.2.1 | 5 / 4 | |
| 0.2.0 | 5 / 4 | |
| 0.1.4 | 5 / 3 | |
| 0.1.3 | 5 / 3 | |
| 0.1.2 | 5 / 3 | |
| 0.1.1 | 5 / 3 |
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
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 (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-04-17, but kobe-kwanten-wisemen 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.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
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 (jorenvandeweyer) than the most recent previously approved version (maartensijmkens) on 2025-04-11, but jorenvandeweyer 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.2.18
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 (maartensijmkens) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-04-02, but maartensijmkens 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.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
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 (kobe-kwanten-wisemen) than the most recent previously approved version (maartensijmkens) on 2025-03-26, but kobe-kwanten-wisemen 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.2.14
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 (maartensijmkens) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-03-26, but maartensijmkens 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.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
2 findingsThis version was published by a different npm account (yuhanghu) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-03-07. It has since remained available on npm for 498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
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 (kobe-kwanten-wisemen) than the most recent previously approved version (maartensijmkens) on 2025-02-20, but kobe-kwanten-wisemen 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.2.0
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 (kobe-kwanten-wisemen) than the most recent previously approved version (maartensijmkens) on 2025-02-19, but kobe-kwanten-wisemen 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.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.