@meta2d/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() deserializes user-defined draw functions from diagram store data; expected pattern for this canvas/diagram engine. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed legitimate by SLSA provenance attestation; consistent with CI/CD adoption. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @meta2d/core is a canvas diagramming library, not a typosquat of cors; name similarity is coincidental. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() compiles user-supplied pen/animation scripts in a diagram engine — expected and documented behavior for this package. | ai |
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 1.1.28 | 2 / 3 | |
| 1.1.27 | 2 / 3 | |
| 1.1.26 | 2 / 3 | |
| 1.1.25 | 2 / 3 | |
| 1.1.24 | 2 / 3 | |
| 1.1.23 | 2 / 3 | |
| 1.1.22 | 2 / 3 | |
| 1.1.21 | 2 / 3 | |
| 1.1.20 | 2 / 3 | |
| 1.1.19 | 2 / 3 | |
| 1.1.18 | 2 / 3 | |
| 1.1.17 | 2 / 3 | |
| 1.1.15 | 2 / 3 | |
| 1.1.14 | 2 / 3 | |
| 1.1.13 | 2 / 3 | |
| 1.1.12 | 2 / 3 | |
| 1.1.11 | 2 / 3 | |
| 1.1.10 | 2 / 3 | |
| 1.1.9 | 2 / 3 | |
| 1.1.8 | 2 / 3 | |
| 1.1.7 | 2 / 3 | |
| 1.1.6 | 2 / 3 | |
| 1.1.5 | 2 / 3 | |
| 1.1.4 | 2 / 3 | |
| 1.1.3 | 2 / 3 | |
| 1.1.2 | 2 / 3 | |
| 1.1.1 | 2 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.99 | 2 / 3 | |
| 1.0.98 | 2 / 3 | |
| 1.0.97 | 2 / 3 | |
| 1.0.96 | 2 / 3 | |
| 1.0.95 | 2 / 3 | |
| 1.0.94 | 2 / 3 | |
| 1.0.93 | 2 / 3 | |
| 1.0.92 | 2 / 3 | |
| 1.0.91 | 2 / 3 | |
| 1.0.90 | 2 / 3 | |
| 1.0.89 | 2 / 3 | |
| 1.0.88 | 2 / 3 | |
| 1.0.87 | 2 / 3 | |
| 1.0.86 | 2 / 3 | |
| 1.0.85 | 2 / 3 | |
| 1.0.84 | 2 / 3 | |
| 1.0.83 | 2 / 3 | |
| 1.0.82 | 2 / 3 | |
| 1.0.81 | 2 / 3 | |
| 1.0.80 | 2 / 3 | |
| 1.0.79 | 2 / 3 | |
| 1.0.78 | 2 / 3 | |
| 1.0.77 | 2 / 3 | |
| 1.0.76 | 2 / 3 | |
| 1.0.75 | 2 / 3 | |
| 1.0.74 | 2 / 3 | |
| 1.0.73 | 2 / 3 | |
| 1.0.72 | 2 / 2 | |
| 1.0.71 | 2 / 2 | |
| 1.0.70 | 2 / 2 | |
| 1.0.69 | 2 / 2 | |
| 1.0.68 | 2 / 2 | |
| 1.0.67 | 2 / 2 | |
| 1.0.66 | 2 / 2 | |
| 1.0.65 | 2 / 2 | |
| 1.0.64 | 2 / 2 | |
| 1.0.63 | 2 / 2 | |
| 1.0.62 | 2 / 2 | |
| 1.0.61 | 2 / 2 | |
| 1.0.60 | 2 / 2 | |
| 1.0.59 | 2 / 2 | |
| 1.0.58 | 2 / 2 | |
| 1.0.57 | 2 / 2 | |
| 1.0.56 | 2 / 2 | |
| 1.0.55 | 2 / 2 | |
| 1.0.54 | 2 / 2 | |
| 1.0.53 | 2 / 2 | |
| 1.0.52 | 2 / 2 | |
| 1.0.51 | 2 / 2 | |
| 1.0.50 | 2 / 2 | |
| 1.0.49 | 2 / 2 | |
| 1.0.48 | 2 / 2 | |
| 1.0.47 | 2 / 2 |
v1.1.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.