@prosemark/core
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package has 7 versions and real download traffic; 0.0.0 reflects early-stage versioning, not throwaway malware. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv is declared in dependencies; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Early-stage scoped package; metadata gaps are not malware indicators given publisher track record. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @prosemark/core is a CodeMirror markdown editor core; name similarity to 'cors' is coincidental. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 6 / 0 | |
| 0.0.8 | 6 / 0 | |
| 0.0.7 | 6 / 19 | |
| 0.0.6 | 5 / 19 | |
| 0.0.5 | 5 / 18 | |
| 0.0.4 | 4 / 18 | |
| 0.0.3 | 4 / 18 | |
| 0.0.2 | 4 / 15 | |
| 0.0.0 | 4 / 18 |
v0.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
2 findingsPackage name '@prosemark/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
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.