filecoin-verifier-common
Advanced tools
filecoin-verifier-common - npm Package Compare versions
Comparing version 1.0.18 to 1.0.19
| { | ||
| "name": "filecoin-verifier-common", | ||
| "version": "1.0.18", | ||
| "version": "1.0.19", | ||
| "description": "", | ||
@@ -5,0 +5,0 @@ "main": "lib/index.js", |
@@ -27,5 +27,5 @@ import { buildPastTwoWeeks } from "./time"; | ||
| DC_REMOVE_COMPLETED: "removalCompleted", | ||
| FIL_PLUS_STORAGE: "source:filplus.storage", | ||
| }; | ||
| //issue open: DcRemoveRequest (to never be removed) | ||
@@ -57,84 +57,5 @@ // RKH due diligence is done: DcRemoveReadyToSign (to be removed only at the end) | ||
| BlockchainSentryEvents, | ||
| buildPastTwoWeeks | ||
| buildPastTwoWeeks, | ||
| }; | ||
| export default common; | ||
| // Happy Scenario | ||
| // 1. Start Application -- client | ||
| // -- Application [Validated] | ||
| // 2. Governance Team Start Allocation -- filecoin gt | ||
| // -- Application [Ready To Sign] | ||
| // 3. Notary Signs (proposal + comment) | ||
| // -- Application [Start Sign Datacap] | ||
| // 4. Notary Signs (approval + comment) (approval) | ||
| // -- Application [Application Granted, Verified Client] | ||
| // Request More Info Scenario | ||
| // 1. Start Application | ||
| // -- Application [Validated] | ||
| // 2. Governance Team Start Allocation -- filecoin gt | ||
| // -- Application [Ready To Sign] | ||
| // 4. Notary Request More Info | ||
| // -- Application [Ready To Sign, Waiting For Client Reply] | ||
| // 5. Client Replies(no template) | ||
| // -- we dont change labels, but increase counter in fe dashboard(fetch only last 7 days) | ||
| // 6. Notary Accepts | ||
| // -- Application [Ready To Sign, Start Sign Datacap] | ||
| // 7. Notary Request More Info | ||
| // -- Application [Waiting For Client Reply, Start Sign Datacap, Ready | ||
| // To Sign] | ||
| // 8. Client Replies | ||
| // 9. Notary Accepts | ||
| // -- Application [Application Granted, Verified Client] | ||
| // Decline V0.1 Scenario | ||
| // 1. Start Application | ||
| // -- Application [Validated] | ||
| // 2. Governance Team Start Allocation -- filecoin gt | ||
| // -- Application [Ready To Sign] | ||
| // 4. Notary Request More Info | ||
| // -- Application [Ready To Sign, Waiting For Client Reply] | ||
| // 5. Client Replies(no template) | ||
| // -- we dont change labels, but increase counter in fe dashboard(fetch only last 7 days) | ||
| // 6. Notary Decline | ||
| // -- Application [One Notary Declined, Ready To Sign] | ||
| // 7. Notary Request More Info | ||
| // -- Application [Waiting For Client Reply, Ready To Sign, One Notary | ||
| // Declined] | ||
| // 8. Client Replies | ||
| // 9. Notary Accepts | ||
| // -- Application [Application Granted, Verified Client, One Notary | ||
| // Declined] | ||
| // Error Scenario | ||
| // 1. Invalid address - add label "Error" and comment "Invalid address" | ||
| // 2. if issue main comment is modified - validate issue again | ||
| // | ||
| // | ||
| // Esraa | ||
| // Happy Scenario | ||
| // 1. Start Application | ||
| // -- Application [Validated] | ||
| // 2. Governance Team Start Allocation -- filecoin gt | ||
| // -- Application [Validated, Notary Review Needed] | ||
| // 2. Notary Signs | ||
| // -- Application [Validated, Notary Review Needed, Notary Proposed] | ||
| // 3. Notary Signs | ||
| // -- Application [Validated, Application Granted] | ||
| // -- Application [Validated, Notary Proposed(Start Signdatacap)] | ||
| // NOTES FOR ESRAA (TODO) : | ||
| // if Otherreason is selected - input should be required | ||
| // Client Verified should be whitelisted label | ||
| // Refer to comment template in message | ||
| // Remove comment template for client and change counter in fe to count only comments posted by person who open the issue && notary is waiting for more evidence(Notary Review Needed) | ||
| // Action points | ||
| // - publish package with correct labels to npm (esraa) (blocker) | ||
| // - integrate with LDN and FE (esraa) | ||
| // - integrate with SSA (fabri) | ||
| // - Script for issue state (fabri) | ||
| // Goal = Finish 19th Of April |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No README
QualityPackage does not have a README. This may indicate a failed publish or a low quality package.
Found 1 instance in 1 package
Improved metrics
- Number of medium quality alerts
- decreased by-50%
1
- Number of lines in readme file
- increased byInfinity%
2
Worsened metrics
- Total package byte prevSize
- decreased by-73.23%
8987
- Number of package files
- decreased by-54.55%
5
- Lines of code
- decreased by-65.54%
153
- Number of medium supply chain risk alerts
- increased byInfinity%
1